Staging Pro > Content produces a 404 Oops! page can't be found message

I need your help. I’ve been trying to figure out why this is happening…

I’m having problems with my staging site. I set up the staging site in a subdirectory of my web site webroot. When I originally set it up all was working fine. I made changes in staging and with the Duplicator plugin I was able to duplicate the site from uam-dev staging site to my live production site in the parent directory. This was flawless and both sites were fine. I was able to go into the staging site and edit Pro>Content pages without any issue. Then after upgrading Slider Revolution I did some work on a slider and some other slider changes without any issues. I went to make some changes to the home page by clicking the Pro>Content menu item and that landed me onto an OOPS! page. I’m able to access the Pro>Content pages in my production admin but cannot access the Pro>Content pages anymore. Below is the URL that is producing an OOPS! page.

See image below

I went into the permalinks screen and clicked the save button, but that didn’t help. I went through the checklist from another Pro Content 404 issue, but nothing has worked yet.

Why am I getting the 404 page?

How can I get this to work again?

I went through the checklist and did all except the CDN…

  1. Ensure everything is up to date according to our version compatibility list. Please follow the best practices when updating your theme and plugins.

  2. If you’re using a CDN, please clear the CDN’s cache and disable optimization services. Don’t have CDN

  3. Test for a plugin conflict. You can do this by deactivating all third-party plugins, and see if the problem remains. If it’s fixed, you’ll know a plugin caused the problem, and you can narrow down which one by reactivating them one at a time.

  4. Remove custom CSS and Javascript from the options or Child Theme and test the case.

  5. Reset your htaccess file by renaming it to .htaccess-bak. Then in WP Admin Menu, go to Settings > Permalinks and just click the Save Changes button.

  6. Increase the PHP Memory Limit of your server.

From the Pro Status page/Report…

Site

Site URL - https://uametry.com/uam-dev

Home URL - https://uametry.com/uam-dev

WordPress Environment

Version - 5.4.1

Debug is on - No

Language - en_US

Is Multisite - No

Memory Limit - 256M

Web Server Configuration

Software - Apache

PHP Version - 7.3.18

MySQL Version - 5.5.5-10.2.29-MariaDB-log

PHP Configuration

Post Max Size - 128M

Time Limit - 300s

Max Upload Size - 128M

Active Theme

Name - Pro

Version - 3.2.3

Folder - //home/sites/9b/4/4a79423d2a/uametry/public_html/uam-dev/wp-content/themes/pro/

Active Plugins

  • Contact Form 7 5.1.9

  • Slider Revolution Before/After Add-On 2.0.6

  • Slider Revolution Reveal Preloaders 2.1.0

  • Slider Revolution 6.2.9

CDN

Click this button to check what CDN this site is using. - Check CDN

From Javascript Console:
/uam-dev/pro/#/content:1 GET https://uametry.com/uam-dev/pro/ 404

jquery-migrate.min.js?ver=1.4.1:2 JQMIGRATE: Migrate is installed, version 1.4.1

/uam-dev/pro/#/content:1 A cookie associated with a cross-site resource at http://www.google.com/ was set without the SameSite attribute. A future release of Chrome will only deliver cookies with cross-site requests if they are set with SameSite=None and Secure. You can review cookies in developer tools under Application>Storage>Cookies and see more details at https://www.chromestatus.com/feature/5088147346030592 and https://www.chromestatus.com/feature/5633521622188032.

2jquery.js?ver=1.12.4-wp:3 [Violation] Added non-passive event listener to a scroll-blocking ‘touchstart’ event. Consider marking event handler as ‘passive’ to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
add @ jquery.js?ver=1.12.4-wp:3
a.event.add @ jquery-migrate.min.js?ver=1.4.1:2
(anonymous) @ jquery.js?ver=1.12.4-wp:3
each @ jquery.js?ver=1.12.4-wp:2
each @ jquery.js?ver=1.12.4-wp:2
ra @ jquery.js?ver=1.12.4-wp:3
on @ jquery.js?ver=1.12.4-wp:3
$ @ x.js?ver=3.2.3:1
(anonymous) @ x.js?ver=3.2.3:1
i @ jquery.js?ver=1.12.4-wp:2
fireWith @ jquery.js?ver=1.12.4-wp:2
ready @ jquery.js?ver=1.12.4-wp:2
J @ jquery.js?ver=1.12.4-wp:2

jquery.js?ver=1.12.4-wp:3 [Violation] Added non-passive event listener to a scroll-blocking ‘touchstart’ event. Consider marking event handler as ‘passive’ to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
add @ jquery.js?ver=1.12.4-wp:3
a.event.add @ jquery-migrate.min.js?ver=1.4.1:2
(anonymous) @ jquery.js?ver=1.12.4-wp:3
each @ jquery.js?ver=1.12.4-wp:2
each @ jquery.js?ver=1.12.4-wp:2
ra @ jquery.js?ver=1.12.4-wp:3
on @ jquery.js?ver=1.12.4-wp:3
$ @ x.js?ver=3.2.3:1
(anonymous) @ x.js?ver=3.2.3:1
i @ jquery.js?ver=1.12.4-wp:2
fireWith @ jquery.js?ver=1.12.4-wp:2
ready @ jquery.js?ver=1.12.4-wp:2
J @ jquery.js?ver=1.12.4-wp:2

/uam-dev/pro/#/content:1 [DOM] Found 2 elements with non-unique id #s: (More info: https://goo.gl/9p2vKq)
<input type=​"text" id=​"s" name=​"s" class=​"search-query" placeholder=​"Search">​
<input type=​"text" id=​"s" class=​"search-query cfc-h-tx center-text tt-upper" name=​"s">​

/uam-dev/pro/#/content:1 [DOM] Found 2 elements with non-unique id #searchform: (More info: https://goo.gl/9p2vKq)
<form method=​"get" id=​"searchform" class=​"form-search" action=​"https:​/​/​uametry.com/​">​…​​
<form method=​"get" id=​"searchform" class=​"form-search center-text" action=​"https:​/​/​uametry.com/​">​
<label for=​"s" class=​"cfc-h-tx tt-upper">​Type and Press “enter” to Search​​
<input type=​"text" id=​"s" class=​"search-query cfc-h-tx center-text tt-upper" name=​"s">​

DevTools failed to load SourceMap: Could not load content for https://uametry.com/wp-content/themes/pro/framework/dist/js/site/x.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE

DevTools failed to load SourceMap: Could not load content for https://uametry.com/wp-content/themes/pro/cornerstone/assets/dist/js/site/cs.0ce70e6.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE

Hello Charles,

Thanks for writing in! Since you have the basic troubleshooting already and yet the issue still exists, kindly provide us access to your site so that we can check your settings. Please create a secure note with the following info:
– Link to your site
– WordPress Admin username / password

To know how to create a secure note, please check this out: https://theme.co/docs/getting-support

Regards.

@ruenel, I added the secure info.

Hello Charles,

The given credentials do not work for us. It seems that the password is incorrect.

Please double check.

Sorry about that. I updated the pwd.
Thanks,
CJ

Hey CJ,

I’ve set your Permalinks to Plain and Pro’s interface worked.

image

That means you have a pretty permalinks issue in your staging site setup and not Pro.

Your web host is likely not allowing or technically disabled mod_rewrite to work in sub-directories. You need to contact your web host for this because otherwise, you can’t use Pretty Permalinks in your staging site.

Hope that helps.

Yes! It does help.
Hmmm. Ok. I will contact them about this.
Can it be left on Plain in dev and Pretty in production?
Thanks again!

Hello Charles,

The permalink settings will be applied to both the WP Admin and the front end of the site. For the meantime while you are waiting for your webhost, it is best that use plain urls while building the site or editing the pages. You can then set your pretty permalink again once you are done building/editing and ready to go live.

Hope this helps.

Yep! It helps.
Thank you @ruenel and @christian

You’re most welcome Charles.

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.