Hi there,
Could you please let us know what issue you were exactly facing with WP Job Manager, and editing class-wp-job-manager-ajax.php helped with that?
We can test it on our side and take action accordingly.
The ajax request wouldn’t return anything, seemed like the variable [‘html’] would crash the page if it was too long. If I added that after the ob area it fixed the issue though.
Hi @someguy9
Thanks for providing more details about that; I have raised this with the development team.
Best,
Hello @someguy9,
Thanks for bearing with us while we were checking this with our developers. Upon further investigation, our tech team wonders if there is any possible local limitation at your end causing what you reported (perhaps a memory limit?)
It’d be helpful if you could share the HTML example you mentioned you flushed there to estimate its size and figure out whether there might be limits in configuration.
I also have opened a GH issue for the sake of documentation; you’re welcome to follow along there and add any information that can be useful for us:
https://github.com/Automattic/WP-Job-Manager/issues/2302
Thanks!
I am using a basic spinupwp install. The issue only happens when there are like 30+ listings to be returned (I manually played w/ the array size). That being said I used query monitor and the memory limit wasn’t near being reached/tried increasing it. Just seems like it’s unable to keep context when the buffer is large or something so it returns nothing.
Hi @someguy9
Thanks for clarifying! I’ve added that to the Github issue that my colleague Stef started, and I’d highly suggest following things there so you don’t miss anything:
https://github.com/Automattic/WP-Job-Manager/issues/2302
Best,
