Hello,

I recently copied my site chesapekeregional.com to dev.chesapeakeregional.com. Unfortunately when I did this, it made it so I could no longer edit the home page on the production site. I can still edit the home page of the dev site though. When I click the "Edit" button on the home page of the production site, it simply loops back to the home page without opening the front-end of the site and adds a # to the URL. You can see what I mean by "Edit" button here. http://imgur.com/a/MBczE

I checked the settings in Content Types and Views on both the production and dev sites but didn't see a difference.

Beyond that, I'm not sure where to look to check for differences in settings/code. I know this may be a database issue. If that's the case, what should I do there?

Comments

VM’s picture

I don't see how copying a database and files would cause this type of issue.

I'd clear the database cache and test.
I'd copy the relative path from the dev. site and paste it into my browser to target the prod site and test.

smpomory’s picture

Thank you for the response.

It appears the issue is that the overlay is actually being redirected when I go to open it. Using Chrome's Inspect tool, when I click on "Edit" and watch the Network log, I find a 301 for "home". The initiators are http://chesapeakeregional.com/sites/default/files/js/js_C-VvHUGUGdtOvMiD... and http://chesapeakeregional.com/sites/default/files/js/js_mjUi0wflDli413YN....

I tried commenting those out in the settings.php but they simply run again. Do you know how to get rid of those?

VM’s picture

those are aggregated .js files. disable .js aggregation, clear database cache and test

smpomory’s picture

I turned off Aggregate JavaScript files and then cleared all caches in the Performance window under Configuration and still experience the same issue.

Do you have any other ideas?

ratewatch’s picture

Any luck with this? Experiencing the same issue.

smpomory’s picture

Hey, it's been awhile so I don't remember how I fixed the issue entirely but, I believe that it had to do with the AdVagg Module. I believe I had the deferred JavaScript Execution option selected, which caused just about everything on the site to run poorly.

Beyond that, I'm honestly not sure. I manage a few different sites so some of this stuff just runs together in memory.