Forum Replies Created
-
Posts
-
@mnlearth– This will be fixed in v0.9.9.3
@rcreators— I fixed your Workflows and just emailed them back. You had two issues:
1) PAGE: The page you want the Workflows on is
admin.php?page=wp_hr_settings, so the page parameter should look like thisPage: admin.php, wp_hr_settings.2) TAB: In your settings/ files you need to let Piklist know what tab you want the settings to display on.
Let us know if you need any more help.
@justin– You’re pretty close. You actually need TWO Workflow files to make this work.
HEADER File: Which is what you have and should work.
TAB File: Take a look at demo-common.php in the demos Workflows/ folder. That’s what is actually creating the tab and setting the default.Let us know if that fixes your issue.
@mnlearth– Thank you so much for giving us access to your site. The issue is fixed! We will release the fix in 0.9.9.3 as soon as we fix a few more issues.
@rcreators– Please zip up and email your code to [email protected] Happy to take a look at it.
@mnlearth– Unfortunately, some custom code you write may have to be updated to the new format. There is no way around this. You will find the new array structure much easier to work with. We don’t anticipate ever doing something like this again.
@horecny– Welcome to the Piklist Community!
I just pushed an update to WordPress.org that should help us debug this for you:
-Update WP Helpers to v1.8.6
-Go to the DEVELOP Tab.
-At the bottom is a textarea under the new DEBUG section.Please copy all that information and email to [email protected]
Also, let us know which version of Piklist you are running.
Thanks!
Please test with our beta version.
https://piklist.com/2015/10/06/piklist-v0-9-9-public-beta-and-next-steps/If anyone runs into this issue again, please don’t fix it by resetting your db. Email us at [email protected] We need to examine a broken site.
@mnlearth– We changed the buttons because we thought they were too distracting. Would love to hear what others think.
Saw your other tickets… both are great catches. We’ll look into a fix.
@mnlearth– Thank you for identifying this issue and submitting a patch. We will review and release a fix.
