Tag Info

New answers tagged

0

The previous developer had hard coded update_option('siteurl','http://example.com'); update_option('home','http://example.com'); in functions.php which on being removed resolved the issue. Thanks everyone for churning in your suggestions.


1

It's possible but requires help from an official WordPress support person (aka "Happiness Engineer") to do it: As for stats, they can also be moved, but staff have to take care of that. Once you have Jetpack installed on the new WordPress.ORG install, post the relevant URLs in this forum thread and then add the "modlook" tag n the column on the right. ...


1

Here are two possible solutions, both of these are actually generic MySQL version control tools but can be adapted to your workflow: dbv.php This tool creates "migrations", which are basically SQL scripts, from the changes detected on the database. These scripts are stored in a local directory and thus can be commited to your current VCS (git, for ...


0

Making content (database) changes on a staging environment is never recommended. You should only use a local/staging environment for template changes. Then, update your theme/plugins (the wp-content folder), and push those files to the live site. Once that's completed, you can then populate the content. Database merging/synchronization is it's own ...


0

Solved: this was a folder permissions issue which was fixed with a chmod to the parent folder containing the affected assets. The appropriate permissions level in this case was 755. Hardening WordPress


1

Found a problem. Basically there were 2 options that forced my permalinks to https: Settings > General: change the site url from https to http. SEO by Yoast plugin, under section permalinks needed to change Canonical Settings to force HTTP.


1

Is the site still working/displaying properly , other than this error on the front end? It looks to me like your new hosting environment has warning and notice reporting ON. Consider looking in your wp-config.php file for WP_DEBUG and make sure it's set to false. Depending on how much control you have on your hosting environment, you should contact your ...


0

.htaccess is not a problem for that, but be care with security. I'm searching and I found the solution here: Giving WordPress Its Own Directory 1- Check your index.php (located at 'public_html') and write on: require( dirname( __FILE__ ) . '/<your-tree-directory>/wp-blog-header.php' ); in your case: require( dirname( __FILE__ ) . ...


0

Did you update the URL in the DB? It sounds like the site still thinks it's running in the old location which usually indicates the DB still has the old path in it. I highly recommend the Search and Replace tool that Interconnect IT produces. The stable 2.1 version is my preference. Make sure you remove this script when you have finished. It's an open ...



Top 50 recent answers are included