I’ve just tested this and didn’t see the problem. To see what’s going on, you should use your Browser Dev Tools inspector to find the element in the HTML and see if it is being hidden by CSS.
Thanks. I could finally track it down to some JS code that interfered.
Strange, the behaviour is sometimes back again and then later on the info box might shows up again. The only info from the debugging log is the:
Cannot modify header information – headers already sentin /home/xxx/xxx/wp-content/plugins/participants-database/classes/PDb_Session.php on line 380
that keeps being logged. I understand that this could be due to another plugin/theme sending output earlier. However, the “Cannot modify header information” is also being logged just navigating through the admin settings, so it should not be related to this behaviour on the frontend.
The only time the info box always shows up is when I deactivate the Participants Login Addon Plugin.
There is nothing visible in the Browser Dev Tools html, the part:
<div class="pdb-message"><p data-field-group="" data-field-name="" class=" pdb-message- pdb-message-">UPDATE-TEXT</p></div>
is just not “always” generated.
I also noticed, that when I force an error message (when a required field is missing) to show up, it always is being displayed. And right afterwards the next successful update shows the success message again.
I’m trying to duplicate this behavior here, can you tell me something more about your setup? Are you using the cookie option?
From your description, it sounds like when the message isn’t shown, it isn’t being hidden, it’s just not present in the html, correct?
That’s right, its not hidden, it is not in the html code. However, maybe it could also be, that this occurs when I’m filling out the form as an admin logged in. I’m using the alternate session method.
Well, of course try it while not logged in, it’s convenient to use an incognito browser window for that. It could be related to the fact that the plugin can’t write a cookie. Sometimes this happens because of php error messages, so if error messages are off, the cookie works fine.
