[Plugin: SpeakUp! Email Petitions] Petitions list blank

You probably have set the petitions table to display 0 rows.

To fix, go to the Settings (Einstellungen) page and change the value of the “Petitions table shows” (Petitionen Tabelle zeigt) field to a number greater than 0 rows (Zeilen). The default setting for this field is 20.

I just installed the plugin, created a petition. The petition shortcode doesn’t work, and Email Petitions list blank, like semih44. Settings are default (display 20 rows). The shortcode it gave me was [emailpetition id=”0″]. I’m guessing it shouldn’t have produced “0” as an id. ??

I tried creating another one. Same thing. Made a change (removed Twitter text) and clicked Update. See resulting blank screen with cryptic message here: https://www.swinggraphics.com/Petitions-screenshot.png

This happens even on a clean install with all other plugins disabled.

Hmmmm…seems if I leave the Twitter message blank, it’s okay. Guess I’ll hide that field with CSS…

A couple of people have had problems with the first petition they create after install not getting saved to the database. This always seems to clear up with the second attempt though. So, I doubt that the Twitter thing had something to do with it. I haven’t ever been able to duplicate this, so it’s kind of hard to troubleshoot. If you can give some more info about the version of WordPress, PHP and MySQL you are using, that might help.

The cryptic message in your screenshot is the strange error message that WordPress displays when a nonce doesn’t match up. Basically, WP thinks that you are submitting the form from a website other than your own WP admin. It’s a security feature and I’m not sure why it’s being triggered here.

The “0” is an indication that the petition wasn’t saved to the database. This number reflects the unique id of the petition that was just added to the DB. Since it’s O, nothing was created.

Do you have an error log or anything else that might show what went wrong when you submitted the form?

It seems to have been fixed now!