Forum Replies Created
-
AuthorPosts
-
Thank you that did the trick for pp_important_messages3 but the check_plugin_updates-hide-my-wp is still there at the top. I run the cron event and it is still there, I delete the event, and it is still there. (All that through the wp crontrol plugin)
I’m sorry but I can’t see this reply, it’s been marked as private. should I start a new thread?
Can you tell me how to disable those crons in child functions.php or provide a fix for this? thank you
Any updates? Can i disable those 2 crons in child theme functions.php? I can manually download and install the plugin every time it’s udpated.
Was there any solution for this, I have the 2 cron jobs
pp_important_messages3
check_plugin_updates-hide-my-wpStuck at the top of the crons.
The issue sometimes is also reported by /wp-admin/site-health.php in WP 5.2
March 22, 2016 at 3:37 pm in reply to: 500 internal error because of two lines in the htaccess #8565Hi there has been nearly a month I still haven’t got any answer from Sr. support. So when somebody can can look into this?
Thank you
February 28, 2016 at 8:43 am in reply to: 500 internal error because of two lines in the htaccess #8223Hi
Thank you
I think what’s left is the nginx configuration as a reverse proxy, the problem has to be somewhere there. Let me know if you need to have a look to any configuration files of nginxFebruary 27, 2016 at 10:13 am in reply to: 500 internal error because of two lines in the htaccess #8210This reply has been marked as private.February 26, 2016 at 6:19 am in reply to: 500 internal error because of two lines in the htaccess #8189As already said in my second post I’m not allowed to give admin access to anybody but I can provide information logs screenshots files and whatever details you may need, just tell me what do you need to debug this
February 25, 2016 at 9:18 pm in reply to: 500 internal error because of two lines in the htaccess #8180Hi Suman,
unfortunately that’s not a solution and we must find a fix for this, We have already bought two licenses and I’m thinking about buying for all our wordpress sites. Is there anybody else who can help us with this? or do you need any more information from me? What’s the correct way to debug this?
I appreciate your time
thank youok I’ll be waiting thank you
Yes that does the trick but layerslider doesn’t load anymore
February 25, 2016 at 1:52 pm in reply to: 500 internal error because of two lines in the htaccess #8155What you said works fine, I have already tested several configurations. The only 1 thing that breaks the wp backend is the PHP restriction which when ticked adds the 2 lines above in the htaccess and breaks only the backend. Either in that case the frontend works fine.
Doesn’t the fact that I use nginx as a revesre proxy mean that I should use an alternative configuration and not the htaccess rules?
This reply has been marked as private.This reply has been marked as private. -
AuthorPosts