- This topic has 11 replies, 4 voices, and was last updated 4 years, 9 months ago by
.
-
Posts
-
-
Greetings!
If you’re currently using 0.9.9.13 I just want you to be aware that if you view the releases on Github you’ll now see 0.10 Beta 1. This is the same exact release, we only changed the version.
The reason for this is because the difference between 0.9.9.12 and 0.10 is somewhat significant. There were considerable portions of code that were rewritten and optimized, fixing many of the bugs experienced. To better communicate this we bumped to 0.10. Also, since we haven’t released this on WordPress.org this is still considered a beta, which we greatly appreciate your testing, although we believe it’s even more solid than 0.9.9.12.
Please continue to test it out and make issues and pull requests so we can make it’s final release as solid as possible.
Thank you for helping to make Piklist even better! It’s a community effort!
-
-
-
Hi @Jason, I recently started using Piklist.
My first question, I posted on WordPress.org and piklist.com as was not sure which is the right one to get quicker turnaround.
Installed 0.9.9.13 yesterday as I am unable to make advanced post relationship work and posted issue here
Now that code is hosted on Github, just wanted to confirm if- Github will be the place to post future issues OR
- Should we post only new version issues there OR
- There will be an initial phase when issues need to be posted at both places i.e new ones on Github and continue with old ones here till everything is migrated to github
As per the initiative to involve community, I assume #3 might be the case but just wanted to confirm so as to not duplicate the issue mentioned above on Github.
Thanks
-
Hi @bhushanjawle!
Sorry you’re having issues with the relate functionality. You’re definitely doing something pretty advanced, which is awesome. I know it’s supported, there must be a bug we need to find (or there’s a syntax I’m not remembering).
Otherwise great question!
We don’t have any present plans on removing the forums. Currently users can get support on the plugin page on WP.org, here, and now Github. I would say that, at least for now, I would recommend that our users that are developers start taking advantage of the issues on Github. The reason being that it’s better suited for exchanging code, referring to other issues/pull requests, and allowing us to organize issues with labels and milestones.
Let me know if this makes sense!
-
-
New issue created on Github
-
-
I’m having the hardest time with the Beta version. I’ve turned off everything plugins and themes so that I could turn off version 9.9.12. Installing the Beta version throws this error on the user Admin edit page. And I still just see the piklist demos tabs and not just the user admin area normally seen:
Warning: end() expects parameter 1 to be array, null given in /Users/alicia/Sites/cazoozwinner.dev/wp-content/plugins/piklist-0.10-beta.2/parts/shared/admin-workflow.php on line 68
On the demos:
Taxonomy Error:
Warning: File does not exist: .php in /Users/alicia/Sites/cazoozwinner.dev/wp-content/plugins/piklist-0.10-beta.2/includes/class-piklist.php on line 530
Demo Settings:
Warning: end() expects parameter 1 to be array, null given in /Users/alicia/Sites/cazoozwinner.dev/wp-content/plugins/piklist-0.10-beta.2/parts/shared/admin-workflow.php on line 68Not sure what I’m doing wrong….
-
-
@intrepidrealist just to be clear, these are warnings and, while they shouldn’t exists, they don’t seem to negatively affect any of the functionality. That just means that you have WP_Debug turned on and have it set to display errors. Otherwise those would happen silently. Again, they will be fixed, I just don’t want you to think they’re major. 🙂
-
@jason Oh thank you!!
I’m using Desktop server and the errors or warnings look MAJOR, see attached image.
I’ll remember to hit Github. Wasn’t sure if it was just me!
Should I stick with the Beta right now or reactivate 0.9.9.12? -
Hi @intrepidrealist!
Yeah… all errors in PHP look catastrophic. Hahah! If you look in the top-left of the message you’ll see “warning”, which is your only indication that it isn’t an error (it would say error if it was).
Typically, unless you’re actively developing, it’s recommended to keep WP_Debug false in your wp-config.php file. And on production you should never have that turned on. Warnings are there just for developers. It means that PHP didn’t like the way something happened, but was able to handle the situation anyway.
And thank you for reporting! Even if it is just you we want to know so we can either improve Piklist or help guide you to a solution.
-
- You must be logged in to reply to this topic.