Forum Replies Created
-
AuthorPosts
-
mcmasterMemberHurrah!! Thanks, Steve! Love you guys. 🙂
mcmasterMemberI just spoke with Kevin. He’s been under the gun most of the year and is just starting to come up for air again.
I’ve been frustrated as well, but I know he is committed to Piklist and I have faith that they will continue to support it going forward.
Donna
mcmasterMemberI was able to resolve my problem by updating Piklist settings. I disabled Preview for all shortcodes.
mcmasterMemberJust ran into this myself. Any ETA on the fix? Thanks!
Donna
mcmasterMember@kutyadog, it depends on exactly what you are trying to do. The problem with grouped fields in shortcodes has not been fixed. I think they may be trying a different approach to the problem.
I was able to simulate flexible content by creating a shortcode for each type of content panel. For the simpler ones, e.g., a blockquote or a box with image and text, the content is edited directly into the shortcode. For panels that require add-mores, I have a separate metabox for creating an add-more and the shortcode just references it.
It’s a kluge but it works and my client is comfortable with it. If you would like more details, let me know and I’ll answer as well as I can.
Donna
mcmasterMemberUpload Errors:
export_widget_record.sql: Sorry, this file type is not permitted for security reasons.Upload Errors:
widget-before-update.txt: Sorry, this file type is not permitted for security reasons.Upload Errors:
export_widget_record.sql.zip: Sorry, this file type is not permitted for security reasons.I give up.
mcmasterMemberOkay it didn’t like the text version either. Apologies as this zip file will probably have one of those MAC .DS_STORE files in it.
mcmasterMemberOops it didn’t like my .sql upload; try this.
mcmasterMemberUpdate: The update not terminating was a separate problem, not related to the widgets, and I’ve resolved it.
I’m guessing that the widgets mess is related to the serialized string problem that has been so frustrating: https://piklist.com/support/topic/0-9-9-6-add-more-problem/
This is because the serialized array that holds the three widget entries had indices of 2, 3, and 4. (See attached file.) My experience is that if they don’t run from 0 to n-1, they don’t work consistently. I tried editing the database entry to fix the indices but it didn’t help.The good news is that I was able to create a nice clean new set of widgets and all is well on my site. I will leave the testbed up for you.
mcmasterMemberWhenever Piklist prompts me to run the update, it runs for at least 15 minutes without terminating. I have repeated these steps half a dozen times, including once with all plugins disabled except for Piklist.
I decided that the simplest solution is to delete the widgets and re-create them from scratch using Piklist 0.9.9.9. But I wanted you to be able see what needs fixing or test your latest code, so I cloned it to a test site and sent an email with credentials to [email protected].
Donna
mcmasterMemberWhat I’ve learned so far is that the serialized array is modified during the Piklist update. I’ve tried running it again from the original database a couple of times, and the update isn’t terminating, which leads me to believe that it probably didn’t terminate the first time and I just didn’t realize it.
I need to head out now but tomorrow I’ll attach the parts/widgets files plus database for the widget fields before and after migration.
mcmasterMemberI just ran into the same problem when updating a site from Piklist 0.9.4v to 0.9.9.
On the front end I get the following error messages:
Notice: Undefined index: render in /Users/donna/Sites/oema/wp-content/plugins/piklist/includes/class-piklist-universal-widget.php on line 289 Warning: Invalid argument supplied for foreach() in /Users/donna/Sites/oema/wp-content/plugins/piklist/includes/class-piklist-universal-widget.php on line 289In the sidebar part of the Widgets edit page, the widget type has been lost and I see the “Select a Widget” dropdown with these three error messages for each widget:
Warning: Illegal offset type in isset or empty in /Users/donna/Sites/oema/wp-content/plugins/piklist/parts/shared/widget-select.php on line 50 Warning: Illegal offset type in /Users/donna/Sites/oema/wp-content/plugins/piklist/parts/shared/widget-select.php on line 67 Warning: Invalid argument supplied for foreach() in /Users/donna/Sites/oema/wp-content/plugins/piklist/parts/shared/widget-select.php on line 67There are three widgets, each with a text field, and two of them are now empty. The third still has a value.
I’m working on it now; will update when I get it working again, and would welcome any suggestions. 😉
Thanks,
Donna
mcmasterMemberNo time today; will test this weekend if not sooner.
mcmasterMemberThank you for this information, @cyclissmo. I think this will also solve the problem I reported 3 weeks ago in https://piklist.com/support/topic/tabs-not-working-in-settings/.
-
AuthorPosts