Posted: May 10, 2022 at 1:35 pm
|
I always get following exception on my ste. I also renewed my license that I can update to newest version of ee but it didn’t help anything. Ein Fehler vom Typ E_ERROR wurde in der Zeile 1786 der Datei /var/www/html/citydance/wp-content/plugins/event-espresso-core-reg/core/third_party_libs/pue/pue-client.php verursacht. Fehlermeldung: Uncaught Error: Attempt to modify property “response” on bool in /var/www/html/citydance/wp-content/plugins/event-espresso-core-reg/core/third_party_libs/pue/pue-client.php:1786 |
|
and also this one: Fehler-Details |
Hi there! Thanks for contacting us! Could you please provide me with more details about how you reproduce this error? Is it show up when Event Espresso is activated, or do you need to send an action (create an event, click on a button, etc.)? Also, check this article: https://eventespresso.com/wiki/troubleshooting-checklist/ that is useful to solve this kind of problem sometimes. I am waiting for your comment on this! |
|
|
Hello, |
Hi there, The error you’ve posted in your initial post usually happens when something is hooking in to prevent updates on the site. So starting with that issue, are you blocking updates? Or using a plugin to block updates on the site? — The second issue posted, usually means either you’re hitting a limit on your server and EE is missing values it is expecting, or something is hooking into the sav call and altering what EE is expecting to be there. If you create a new Event within EE, just give it a title and then publish, do you see the above error? |
|
|
Hello! |
Hmm, so you’re getting that error on page load, that’s different. Can I take a quick look in the admin to see if anything stands out? If so you can send temp login details using this form: |
|
Hi there, What is the history of this site, please? The reason you are getting the fatal errors mentioned is because the default pricing within Event Espresso has been removed from the database. We don’t have a user interface to remove that as it it critical data for EE to function so has someone manually altered the database previously? |
|
|
Thank you for the information. |
The first would be the missing default ticket within Row 1 is usually the default ticket with You may have missing values from |
|
|
I have some backups of the database but in the backend I can only restore the whole db. |
Did you recently alter the Database tables then? I’m just wondering how they have gotten to the current state with missing values. Can you send me the current version of the database so I can load it up locally and take a look? (I only need to see the |
|
|
I did not change anything yet. |
Host it somewhere and send the link we can use to download it to support[at]eventespresso.com (If archiving into a .zip you could set a password on the zip file and add the password here in a private reply, I’ll remove it shortly afterwards) |
|
|
Did the link work? |
|
Hello! |
Hi there! We are currently checking what you’ve sent to us. |
|
Ok, so I assume you are comfortable enough with phpMyAdmin to be able to make a change within a table, correct? The row for the default pricing ticket is still within the database, but somehow the flag set on that row to show it is a default price is now set to 0 (it should be 1). The same is also true with the default pricing. Eent Espresso wont set these values, there’s no option to disable the last default ticket/price within the UI. Did you make changes to the database manually? (Again I’m just wondering how this how it has ended up like this) Backup the database again as it is now, then the fix I would use is to edit the Like so: https://monosnap.com/file/uWPxxOcf1hcdk6sf12OjkN4DwWJ0pq Then similar in Now when you create an event a default ticket with a price should be assigned to it, the reason you are getting the fata currently is no ticket is within the event and EE always expects at least 1 ticket. |
|
The support post ‘Exception’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.