Forum Replies Created
-
Posts
-
@cezarion– We added a feature to the latest version of Piklist. Read about it here >
Let us know if it works for you.
@shayneol– We’re getting closer! Two things:
1) Please post the exact code that is not working.
2) Let us know which group cannot be repeated more than 10 times.@shayneol– There were two issues:
1) Try downloading again. There were some old files still on WordPress.org.
2) Even with the old files, your admin shouldn’t have looked like that. Make sure you don’t have another version of Piklist running, or it hasn’t been included in some other plugin or your theme.Let me know if this works.
@shayneol– Please verify that you only have ONE version of Piklist installed, and it’s 0.9.9. You should not be receiving that Workflow message in the Piklist Demos.
I tested in the new version and it looks good to me.
@vayu– Thank you for helping us spot a bug in the updater code.
Let us know if you need any more help.
Try replacing
piklist/parts/updates/0.9.9.phpwith this file.And then run the update again.
@vayu– Sorry you’re having so much trouble. Let’s try to debug this:
1) Open the update page in Google Chrome
2) Open inspector and click on the “Network” tab.
3) Run the upgrade.
4) Click on the last file to run. You should see an error message. Paste the message or screenshot here.I attached a screenshot of the inspector screen
@vayu– Welcome to the Piklist Community!
Please delete the following files. WordPres.org SVN didn’t delete them.
/includes/class-piklist-notices.php
/includes/class-piklist-pointers.phpNotice the PLURALS in the file names: noticeS and pointerS.
The singular versions should just be there.Let me know if that fixes your issue.
@cezarion– We are able to reproduce this issue and are working on a fix.
That shouldn’t happen. Are you sure it’s publishing? Is it already published?
Please test with the Piklist Demos and see if it’s the same.
If you are still having an issue please post your code here.
@hartey11– Welcome to the Piklist Community!
Please make sure this code is in your /parts/settings/ folder.
If it is and it’s still not working, please zip up your plugin and email to [email protected] so we can debug it for you.
