Let’s see two examples to understand my problem better.
Example #1: User installs a new WP plugin, e.g.: Google maps shortcode, which outputs the div of the map and some scripts after that to start the map. When I call this page (where the google map shortcode is placed) the scripts won’t (always) work.
Example #2: User installs a ToolTip plugin. But this plugin won’t print any scripts after the shortcode, instead it prints its own script in the head and executes it when the document is ready, e.g.: $(‘a.icon’).toolTip(); This script also won’t work because first I need the content elements from the AJAX call, I can apply the function after that only. Of course if I put it into success callback, it works. But should the user put every new JS function into this callback function? How should I handle this well?
Extra info which may help: I use jQuery.load() function and I only get the #content div from the loaded pages, not the whole page.
Idea as possible solution #1 (not tested yet): get script tags from AJAX loaded content and eval() them?
So, Envato, here’s the list what the marketplace needs:
- Raise standards a little bit to filter those cloned and same looking themes
- Better homepage layout to showcase new items
- Better review/approval timing, max 30 items/week or let’s say 30 items/5 days (if there are so many quality items), so every author gets his/her 15 minutes of fame
An official response would be great from Envato about this. But NOT the copy-paste one, please. We need concrete things like “A new homepage is coming, expect it in January 3, 2014” OR “We don’t want to replace design, maybe 2 years later when the pipeline is clear”. At least we’d know what to expect.
I’m just guessing but I think maybe it has to do something with that reviewer job opening I saw recently. Maybe submitted items jammed in the queue and now the new reviewer went through them all.
I’m getting really pissed off because of this whole shortcode – autop thing. This bug is there since years and WP still couldn’t solve this problem. Why?
I also think that TinyMCE must go. What WP need is a correct page builder and a default shortcode set which makes it easy for people to build columned layouts and basic things like buttons, place icons, pullquotes, etc. Most clients doesn’t know any HTML code and with TinyMCE you can’t really customize your site without HTML and CSS knowledge.
I think we should think of it like a normal plugin. There must be a general styling included in the plugin, so if you use it in any other theme, it should look good.
AND in your theme’s stylesheet you can add some extra stylings to make plugin’s layout more compatible with your current theme’s design.
You should submit it into PSD template category. That’s the hardest category to get into.
Chances are high that if your PSD design will be approved, your WP theme will be too. Not 100% guaranteed, but you have a better chance.
Theme approval will also highly depend on code quality.