Limited Support
Our team is currently on holiday, so support will be limited during this period. Response times may be slower than usual, and some inquiries may be delayed.
We appreciate your patience and understanding, and we’ll resume our usual support by the end of August.
To Whom It May Concern,
One of my users is reporting receiving Error 2253. I can see from previous threads a solution exists here:
https://wpforo.com/community/how-to-and-troubleshooting-2/error-2253-staging-issue/#post-15419
However, I have the following questions before proceeding:
- If I edit this PHP, will it simply get overwritten the next time the plugin is updated?
- Am I ignoring some root cause problem that needs to be fixed?
- Why is only one user getting this error and not others?
Thanks for any added information before I proceed.
-- Aaron
Apologies - I have just realized the solution I found was for a different error. The error my user is receiving is 2252 (not 2253). Can you please assist? Thanks.
-- Aaron
Maybe not related but you have an issue:
GET https://log.pinterest.com/?type=pidget&guid=1_JZPkJp_HP2&tv=2021110201&event=init&sub=www&button_count=0&follow_count=0&pin_count=0&profile_count=0&board_count=0§ion_count=0&lang=en&nvl=en-US&via=https://peakprosperity.com/community/new-here-start-here/&viaSrc=canonical [HTTP/2 400 Bad Request 134ms]
Press F12 to view it.
Hi @aaronmckeon,
Please read these six topics, the problem have almost the same source and solution: https://wpforo.com/community/?wpfs=2252&wpfin=tag
Hi @robert - Thanks. I have reviewed those threads and they all seem to suggest the issue is with a conflict between URL's. I looked at our general settings and all URL's are the same ( https://peakprosperity.com), which matches our actual domain. It's also strange that this problem has only occurred to one user as best I'm aware, and I cannot duplicate it myself. If it were an issue with URL conflicts, I would think all users would be having a similar problem. Can you let me know if you have any other ideas? Thanks again.
