updating prettyPhoto in child theme

Thanks Peter,
That leads me to one potential conflict, but I don’t know for sure so I will post it and let you tell me if there will be one or not. I just can’t yet wrap my head around php code.

previously I wanted to add a js file for google link tracking. you gave me almost the same code to add a js folder in my child theme and then place the google file in that child js folder. It looks like this…

if(!is_admin()) add_action('wp_enqueue_scripts', 'avia_register_child_frontend_scripts', 100, 1);

function avia_register_child_frontend_scripts()
{
	$child_theme_url = get_stylesheet_directory_uri();

	//register js
	wp_register_script( 'avia-js-child-theme', $child_theme_url.'/js/googlelink.js', array('jquery'), 1, false );
	wp_enqueue_script( 'avia-js-child-theme' );
}

your new code in the above post for prettyPhoto is very much the same. So if I paste your new code after this code in my functions file, i dont know if that will make a potential conflict some how. can I use both as is, or do I need to combine them some how?

Hey Peter,
thanks for combining these for me. Will you please look it over and make sure there isn’t a slight error somewhere. I went ahead and replaced the default prettyphoto js file back into the parent theme, and then placed the modified prettyPhoto file in the existing js folder in my child theme and then placed the new modified code in my child functions file. And now the effect I was previously getting is gone. So it is still reading the parent prettyphoto code.

thanks for looking into this further.

Okay Peter,
I tried that without the 1 and it still didn’t work. Forgive what I am about to say as I know for a fact I am talking out of my shorts, as I don’t really understand php code at all. But figured you are obviously on the right track and tweaking stuff to get it to work. So I looked on the WP codex at the register_scripts, enqueue, dequeue etc to try and learn more about them for my own sake, definitely still way over my head, but on the dequeue script documentation it was talking about adding deregister along with dequeue, but I don’t know in what context as I didn’t understand it. So thought maybe that is the trouble, but what I gathered was the dequeue was turning off the script I think and then the following register and enqueue scripts are turning it back on but in the child theme location. I was just trying to figure out what the lines of code actually do.

Again without knowing anything I thought it was interesting that the dequeue, register and enqueue scripts all had the same name ‘avia-prettyPhoto’ I thought maybe the new child location script name should be different. This is based off the fact that most of the mod functions and filters you and devin have given me in the past seam to have arbitrarily made up names when including them into the child theme. So I simply changed the wp_register_script and enqueue_script name to ‘prettyPhoto’ instead of the ‘avia-prettyPhoto’ that we used in the dequeue-script before it in your code. And it then worked so then I used avia-Photo and it still worked.

So knowing that, will you look at it again and see if I can infact just use some made up new name for those two lines and call it good or is it more sophisticated than that, and that may give you a lightbulb moment to improve the code. Thanks Please advise.

Hey Peter thanks for looking again,
As I mentioned I don’t have any bases to think anything specific, I was just blindly trying things. The previous code with priority 100 and “2.0”, false); worked as long as the register and enqueue name as different than the dequeue.

That being said I have no doubt that the new code will work. but before I implement it, what is more ideal from your end as you know what the script is doing? to have 100 or 10 for the priority and to have false or true after the “2.0”? I saw you changed the latter also.

add_action('wp_enqueue_scripts', 'avia_register_child_frontend_scripts', 100);

function avia_register_child_frontend_scripts()
{
	$child_theme_url = get_stylesheet_directory_uri();

	wp_register_script( 'avia-js-child-theme', $child_theme_url.'/js/googlelink.js', array('jquery'), 1, false );
	wp_enqueue_script( 'avia-js-child-theme' );

	wp_dequeue_script('avia-prettyPhoto');
	wp_register_script( 'avia-newlightbox', $child_theme_url.'/js/jquery.prettyPhoto.js', array('jquery'), "2.0", false);
	wp_enqueue_script( 'avia-newlightbox' );
}

or

add_action('wp_enqueue_scripts', 'avia_register_child_frontend_scripts', 10);

function avia_register_child_frontend_scripts()
{
	$child_theme_url = get_stylesheet_directory_uri();

	wp_register_script( 'avia-js-child-theme', $child_theme_url.'/js/googlelink.js', array('jquery'), 1, false );
	wp_enqueue_script( 'avia-js-child-theme' );

	wp_dequeue_script('avia-prettyPhoto');
	wp_register_script( 'avia-newlightbox', $child_theme_url.'/js/jquery.prettyPhoto.js', array('jquery'), "2.0", true);
	wp_enqueue_script( 'avia-newlightbox' );
}

Thanks for the info Peter.
To wrap this up, after more testing if I use the priority of 10 and true to load at the bottom of the page and the names of the different scripts are identical it does in fact load. With the names the same and the values of 100 and false it doesn’t not load. But with the 100 and false and if I change the name of the new child scripts it will once again load.

So In conclusion I reverted the names to the same (like you started) and used you 10 and true values as my choice to the variables.

Thanks for staying with this to get more clarity.