Forum Replies Created
-
AuthorPosts
-
SteveKeymasterJune 27, 2016 at 11:12 am in reply to: Get Image upload url from settings file field and use it for embedded css #6809
SteveKeymaster@semwangajoshua– That code I posted needs to be tweaked to your SETTINGS and FIELD name. What’s the name of your colorpicker field? When created it, what did you use for the
fieldparameter?Also, what did you register for your settings?
SteveKeymaster@7studio– Welcome to the Piklist community!
Thanks for letting us know. We’ll look into it.
SteveKeymasterCan you reproduce in the Piklist demos?
SteveKeymaster@netpistols– Welcome to the Piklist community!
Try removing the
scopeparameter.
SteveKeymasterEnrique–
You can let WordPress tell you. Try this. It should display the $editor_id for you.
function my_editor_buttons( $buttons, $editor_id ) { print_r($editor_id); // display id return array( 'formatselect', 'bold', 'italic' ); } add_filter( 'teeny_mce_buttons', 'my_editor_buttons', 10, 2 );
SteveKeymasterSorry for any confusion. The 0.9.9.8 release fixed a ton of bugs… but not all. Mostly importantly, it has an upgrade script that reformats the old array structure for add-mores. Now that add-mores are standardized, we can move forward with more updates.
SteveKeymaster@michael– I was able to reproduce.
You can roll back this change by:
-open file: piklist/parts/shared/list-table-post-statuses.php
-Change the one line of javascript to:$('select[name="_status"]').replaceWith('<?php echo $field; ?>');This may cause other issues. I’m not sure yet. Please test and let us know if you see any other issues.
SteveKeymaster@eflouret– Welcome to the Piklist community!
Which hooks/filters/actions are you using to achieve this?
SteveKeymasterGlad you got it working! Closing ticket.
June 20, 2016 at 2:36 pm in reply to: Plugin could not be activated because it triggered a fatal error. #6771
SteveKeymaster@sflemingphotography– You’re going to need to upgrade your version of PHP to at least 5.6, as recommended by WordPress.
SteveKeymaster0.9.9.8 and 0.9.9.8 were part of the beta program. We released to wordpress.org to get everyone on the same version. Unfortunately, not all these bugs were able to be fixed during these releases.
The next big release has these issues fixed.
June 20, 2016 at 1:22 pm in reply to: Plugin could not be activated because it triggered a fatal error. #6768
SteveKeymasterWe just pushed a new version to WordPress.org.
This issue is fixed in v0.9.9.9
-
AuthorPosts