Forum Replies Created
-
Posts
-
At least I’m not all alone 🙂
https://piklist.com/support/topic/attachment-is-too-large-in-admin/Thanks, Steve. Unfortunately the problem remains after a fresh Piklist install (current dev. version), with piklist beeing the only active plugin, the Twenty Fifteen theme active, and inside the demo. So there’s not a single line of code in the mix apart from WordPress itself and Piklist. How’s that possible?
No, not working. After adding more than one add-more, all inputs loose their values, and the heading (‘bub_title_shoplinks_heading’) is being treated as part of the add-more.
I used the exact same code as above without the outer field name. When I add it back in, the fields look fine in the backed but will stop working on the frontend, as experienced before.
I think I’ll confine myself with the simpler variant for now.
That’s exactly how it was before it “suddenly” stopped working and I got “Illegal string offset” messages. However, now after deleting all corresponding entries from the database and trying again, everything works like a charme.
Can this be a result of changing (and changing back) field names after there have already been made entries to the database? Because that’s probably something I’ve done.
Thanks a lot, Steve.
Okay, this kind of nesting seems to be problematic in the first place (empty arrays). Now, after cleaning up the database and removing the outer group, it’s less pretty but it works again, including the default values showing up. 🙂
Also true for the file uplad field, when picking an image. It shows in full size in the backend until it is published.
And of course: When I say the value of the text field isn’t showing, I’m talking about the first text field (my heading) and it’s default value (‘value’ => ‘Kaufen’).
