Archived topic
Oops! That page can’t be found
18 replies · Started by Takis on May 22, 2017
Hello i bought the premium plugin but i can't customize anything.
It says Oops! That page can’t be found.
What is wrong?
Thanks!
Hi there,
All pages are saying this? Or only one page?
All the pages work just fine...
And if i change theme everything is ok....
When i choose generatepress i can't customize anything
What do you mean by all the pages work fine? Which pages are showing the 404 error then?
Customize.php Failed to load resource: the server responded with a status of 404 (Not Found)
i will upload it by ftp and i will let you know....
Customize.php is a core WordPress file.
If it's missing, it means you need to re-install WordPress, or your server is having issues.
Have you contacted their support?
With other themes it's working just fine....
Only with generatepress i have problems....
I will try it and in another site.....
Sorry it was a server issue!!!!!!
So sorry....
Everything works great now...!
No problem :)
Takis,
Could you perhaps elaborate on what the problem was with your server?
I'm getting the same issue. My host, tmdhosting.com, says they can't help. Perhaps you could shed some light on the issue?
Would really appreciate that. I'm stuck in limbo.
Dear friend we have that issue too with tmdhosting!
What we noticed:
It's happening everyday at a particular time. It lasts for about 40 minutes. And then everything it's working again.
During that time that the problem occurs you can't customize the theme. Any theme at any site if you have at your package - let's say - 6 sites.
So far we haven't found a solution. Error logs are clear!
Just to know and if you want to refer to us at your problem at technical support our ticket is #925131
Thanks!
Thanks so much for your reply. I shall forward it to tmd.
Let us know for the issue....
Thank you also!
I have just contacted TMD. I also sent them the link to this thread. Hopefully we can get this sorted.
Good to know you're both using the same hosting. These are the only two reports of this issue, so I'm assuming there's some sort of server weirdness going on.
Hopefully TMD can figure it out.