Thanks,
I’ll test wpdebug on the development branch to see if these errors are still thrown.
No worries,
just thought i’d mention it.
while i’m at it though:
is there any way to not only pull “slides” from post categories but also from custom post types ?
would be really cool
thanks
in the plugin php file, just put the wp_enqueue_script calls in a function (or two functions, for both js init and css init)
then
add_action('wp_head', 'myfunction');
I see more incorrect applied wp functions.
The code of this plugin is quite ugly (at the moment)
Hi pumpkineater,
there was a serious refactor in this plugin code but I’ve decided to continue the development on GitHub to allow contributors to help me.
I know there was improvements to make to the code but I hope that you’ll find the future release less “ugly” : https://github.com/jlethuau/wp-parallax-content-slider/blob/master/wp-parallax-content-slider.php
Since I’ve installed WPDebug too, I also notice that there are several warnings and notices which are throwned by WordPress core itself, so their code must be ugly too I think 😉
On Github, good decision !
You’re right, WP core isn’t the most elegant written piece of software either. But hey, ugliness can be effective, otherwise millions of users would complain about WP 😉
So no offence against the parallax content slider.
It may evolve to better coding and for the moment it is working sort of alright anyway (with some fiddling).
Nothings starts perfect, so your initiative is much appreciated !
It’s just my two cents worth….
P.
