Forum Replies Created
-
Sounds great, Ahmed, but if there’s anything UP needs at the moment it’s performance optimisation.
in reply to: Do we need this feature? Basic Text/HTML NewsletterCan confirm it happens to us from time to time even now.
in reply to: Sometimes syntax error logging inI don’t know if the plugin is even still under active development at this point.
Needing to run at over a GB of memory is insanity.
Anyone?
in reply to: Userpro getting badges from local URL on live site.Or you need a caching plugin.
You’ll need to contact someone with technical expertise or do some googling.
Well without knowing your server configuration and your site load I’d say…probably? Perhaps raise it to 256MB just to be safe. Because unless you’re getting hundreds of simultaneous page requests it’ll be fine, memory will be free (assuming you have 8GB or above).
You can check memory usage by each plugin, work out what’s eating memory.
128 will be enough, unless you’re running A LOT of other plugins.
At a push, 256MB. 512 is crazy.
Agreed, Ahmed, you are certainly doing ajax calls the right way. 🙂
You should copy/paste this thread when people come asking about Syntaxerrors in future.
in reply to: Sometimes syntax error logging in@Ahmed, I verified the JSON parse error as a memory issue (after hours of debugging).
@jeditricks007 Take a look at the network requests on chrome dev tools, when you register/login it makes a call to admin-ajax.php, the output (if there’s not enough memory) will be a returned html page. Something like this:-
<br /> <b>Fatal error</b>: Allowed memory size of 41943040 bytes exhausted (tried to allocate 30720 bytes) in <b>/home/domain/public_html/mydomain.com/wp-admin/includes/post.php</b> on line <b>822</b><br />
It’s expecting JSON encoding though so it says ‘UH NO, PARSE ERROR’. It is FOR SURE a memory issue though.
In my testing you need 64MB or if possible 128MB to avoid this (if you have a lot of plugins running).
UP does use a fair bit of memory… It is a complex plugin though. But I just posted this so you’d know the cause of all the many “syntax error” threads, it’s people running on servers with lots of plugins and low memory.
in reply to: Sometimes syntax error logging inSee my thread. Answer is there.
http://userproplugin.com/userpro/forums/topic/sometimes-syntax-error-logging-in/
Ahmed should pay me for my tireless debugging. 😀
Ok after 6 hours yesterday I’ve finally worked out what causes this, it’s UP eating up server memory.
When logging in UP makes an Ajax call to admin-ajax.php and if you’ve set your server memory too low the response is something like ‘<br /> <b>Fatal error</b>: Allowed memory size of 41943040 bytes exhausted (tried to allocate 30720 bytes) in <b>/home/domain/public_html/sitename.com/wp-admin/includes/post.php</b> on line <b>822</b><br />’
Since it returns an html page in error if memory is too low that’s what it see’s as a ‘syntax error’, since it’s expecting a JSON response.
Depending on how many plugins you’re running you probably need a minimum of 64MB of memory allocated on your server.
Or UP needs to work with caching plugins or no one on shared hosting will ever be able to run it properly.
I repeat, ALL of the syntax errors people are getting are NOT plugin conflicts, they’re just UP eating up server memory.
in reply to: Sometimes syntax error logging inThere is an error in userpro’s script, don’t know if this is the cause.
Uncaught TypeError: Cannot read property ‘width’ of undefined 192.168.1.141:8888/wp-content/plugins/userpro/scripts/scripts.min.js?ver=3.9.1:276
in reply to: Sometimes syntax error logging in