As I read in their plugin-check-info.md, the PHP short tag is actually part of a string and not a real tag. Is that also an issue for not accepting a theme with such plugin?
Also, what about the Warning notices such as fopen(), fclose(), fwrite(), thrown by the Theme-check? Are they not allowed in themes and plugins, as I remember they were included in the exception list by the Themeforest Standard Submission Requirements (Phase One) (a link to which I cannot find…)?
I’m sure someone who actually worked on the framework will clarify this better than me.
Thank you for sharing this fantastic piece of work, it looks like it has everything one needs to create a robust wp theme.
One question though, did you ever receive an answer from Envato regarding acceptance of themes utilizing Unyson framework?
Did anybody who tried this fix experienced this bug – when switching between the Visual and Text editor a couple of times in TinyMCE, both toolbars become visible and I can’t access the Text editor, as if the tab button is dead. When I disable the Zilla plugin it goes back to normal…
Any ideas what might be causing this?
I tried the Zilla Shortcodes plugin fix on a fresh install and with Twentyfourteen theme…
Other than this, everything works as it should…
Yeah, got it now, works like a charm. Many thanks Webbu, you’re a life saver!
I see now that you listed the only two shortcodes in the dropdown, but still not sure why the warning…
Hey Webbu thanks for the tut, much appreciated
I went through all the steps with a fresh download of Zilla Shortcodes, and while the button does appear, I only get two shortcodes listed in the dropdown menu – Alerts and Buttons, and when clicking on Buttons shortcode I get this warning:
Warning: Invalid argument supplied for foreach() in zilla-shortcodes-1.2\tinymce\shortcodes.class.php on line 65
Any ideas on what’s going on?
I swear they couldn’t pick a worse moment for updating the WP, all of the plugins and frameworks I started using, broke down due to TinyMCE 4.0
I really thought I was losing my mind
Yes, the plugin is from the wordpress.org. I was testing the scenario where I would ship my theme with the embedded code and the user updates or installs the plugin on his own.
But still, I don’t know why I couldn’t make the plugin (without the embed code) display my custom option panel. I could only get the demo panel to appear when activated.
to the functions.php all I have to do make my option panel appear in the dashboard. Is that also related to the plugin version?
The repo code works beautifully, and I really enjoy playing around with all the options.
Thanks for the answering me in such short notice.