I have a Wordpress website with Asska Theme template. For some time now, when uploading products to the store / browsing the page / saving changes to the product content, there is a common Internal Server Error. Unfortunately, I do not know where to look for a solution - the logs themselves do not tell me anything, the server has the template requirements set and even more.
I disabled plugins to see if anything would speed up navigating the admin panel itself, but I didn't feel any difference even with limited plugins.
Do you have ideas? The website works normally (currently only password protected in htaccess so that there is no view), but it's so hard to add anything to it that I don't want to work
Plugin exclusions,
optimization,
changes to server settings
Related
I'm just wondering if anyone might of been had the same experience as me before? I have just migrated a WordPress site (running on an older version of WordPress) to a new dedicated server.
My website loads up perfectly fine, however, when my users are logging in or trying to access the WooCommerce Checkout page, there browsers are returning the "Site did not send any data".
The strangest thing is, some people can log-in, others can't. I've advised my users to try deleting there browser cache and I've setup a tempoary log-in link (Incase the old log-in link my users was seeing was being cached from when my site operated on my previous server)
I've disabled all caching plugins, but in the Network tab, I'm still seeing a few elements being cached, I'm not too sure if this could be WP CLI cache which is perhaps operating in the background?
Ultimately, I'm just trying to get my head around how to solve th "Website did not send any data" error - It's been around 4 days since the server migration completed and previously, users had no trouble at all logging in and navigating the website.
Here's what I've tried so far:
Reset the htaccess file
Disabled caching plugins (Third-party plugins)
Installed Really Simple SSL to ensure all my website paths are being redirected to HTTPS
Changed my PHP handler to SuExec
Disabled server-side cache
Reset permalinks (Changed my permalink setting from Post Name to Plain, and vice versa)
But quite a few of my users are still reporting the same error, whilst other users can access and navigate my website perfectly fine.
Has anyone experienced a similar issue before?
Thank you!
I've been asked to help out with a former colleague of mine's Wordpress Site. Nothing crazy, just change the format of a page, and add some kind of form on another page. I'm not so concerned with these changes I need to make, but am more concerned with setting up an identical site locally so that I can exercise these changes, do whatever I need to do, then simply upload my changes.
Quick background of myself; web developer of about 5 years with strengths in the Javascript frameworks and Node sphere. I know what Wordpress is and can navigate through the project with relative ease. Where I fall short is uncertainty in the project set up side of things.
So I have both the project itself and an export of my clients database, and configuration is updated accordingly. When I attempt to run the site I'm constantly prompted with errors, most of which have me take a look at the code and see what exactly the problem is. At this point I've made quite a few adjustments to the site to try and make it work that I feel continuing development won't get me anywhere.
Is duplicating an existing site to a local env usually this difficult? Could bad implementation of the initial site by the previous developer be a reason why I'm now struggling? Am I missing a step?
Duplicating a WordPress website is not that difficult. If you have the wp admin login of your website then you can simply use duplicator or akeeba backup plugin, but no worries, if you do not have the wp login access and just have the wp files & db then try this: create a new db from phpmyadmin, place your files in wp theme directory, install your new wp by using your new db file created, after that import your db file and do the following changes in your wp config file found in your root directory.
You will need to type in the new database information: database name, database user, and the password.
Once you have updated those, click Save Changes
Fixing your Permalinks
Log into your WordPress Dashboard, using the username and password from the copy of WordPress you brought over
Under Settings, click Permalinks
You don't have to make any actual changes, just click the Save Changes button.
Doing this will update all the page and post URLs. If you have custom themes or plugins/widgets with old URLs, you will have to update those manually since there are not any plugins that are able to modify those as well.
For ref:
https://my.bluehost.com/cgi/help/2361
https://www.tipsandtricks-hq.com/how-to-easily-import-or-export-any-of-your-wordpress-database-content-using-phpmyadmin-3415
I have setup the AMP plugin in WordPress but while going to see the AMP pages (Appearence->AMP), I saw an error "Non-existent changeset UUID".
Also there is message in console says,
"Failed to execute 'postMessage' on 'DOMWindow': The target origin provided ('https://test.com') does not match the recipient window's origin ('https://test.ve.staging.wpengine.com')."
Please help me to resolved it out.
I've recently taken over administration of a website that has historically been ... poorly managed, and upon trying to use WordPress' built in theme customizer, I was greeted with the same message: "Non-existent changeset UUID.", although I didn't get any related messages in the console.
Apparently my issue was caused by the fact that one of the people who set up the site to begin with had decided to put the public site at www.example.com and the WordPress admin pages at example.com/__wp.
If this is your issue, you basically have two options.
Make sure to log in at both domains.
This may be a little difficult since WordPress' login page is part of the admin portion of the site and thus only logs you in to the admin portion of the site, however this proved to be a good temporary solution for me as there was a plugin installed which added a login widget on the public portion of the site.
Change the WordPress Address to be on the same domain as your Site Address.
The Option appears under Settings > General, but in my case I couldn't change the WordPress Address setting there and had to go into the WordPress database in our company's MySQL server.
After dealing with the above issues, I discovered that this issue had also caused a bunch of resources to be incorrectly loaded from example.com that should have been loading from www.example.com, as well as a number of leftovers from the site's development that were causing some resources not to load because the database thought they were at localhost.
With the help of another Stack Overflow answer I found a Database Search and Replace Script in PHP by interconnect/it (also available on GitHub) which allowed me to repair the mess previous people had made of the website without making a new mess with incorrectly serialized data, or all of the work of manually, correctly serializing the data I needed to change.
I recently moved my site built in Word Press to another hosting provider and I found the shortcode [woocommerce_my_account] is not working anymore.
Previously, I had a page called account login where I had the shortcode [woocommerce_my_account]. In the settings I set the landing page to be the same page (account login). so, after an user logged in, it was redirected to the same page showing his/her details.
However, in the new hosting provider this is no longer working. After I put the login information and attempt to login it is taking me to wp-login.php page and ask me to enter my login details again.
The URL path that I see in the browser after attempting to login is similar to this <site_name_url>/wp-login.php?redirect_to=http://<site_name_url>/account-login/
Anybody has got to the bottom of this issue? Thank you.
Try adding this to your wp-config.php:
define('WP_HOME','http://example.com');
define('WP_SITEURL','http://example.com');
Make sure you change http://example.com with your own domaine. You can also try to search and replace your domaine in the database if it has changed.
You can also try to clear browser cache and cookies. I had an issue like this before, launched a private navigation and it was working fine.
Try setting define(‘WP_DEBUG’, true);, you may see something going on.
Sometimes, php version makes a difference, try to set the same php version on you new host (google the name of your hosting provider + change php version).
When you move sites/restore databases you often need to save the permalinks again.
go to /wp-admin/options-permalink.php and click "save". This will setup your .htaccess file with the correct information for redirects.
Finally, after all of these days searching and trying different things, the answer for this issue in my case was not related with the Word Press installation itself but, with some software installed on the server called varnish, apparently used to cache the site and improve its performance.
After having a support chat with the hosting provider, they mentioned that varnish is breaking the woocommerce plugin.
At this point, I am not sure if varnish is not compatible with woocommerce or the settings applied on the server using this software make woocommerce not to work properly.
I’m working on a wordpress site, it’s almost finished.
Left it lying on the server for a few weeks after the launch to gather user feedback, and now ready to make some minute adjustments.
Loe and behold, can’t login.
Going to parentsauxassembleesgenerales.org/wp-admin won’t show me the admin page, but will instead redirect.
Sure enough, I had an automatic update to 3.8.2 on April 9 that seems to coincide with the admin access being gone.
Contrary to most redirect errors for login pages after an automatic update on forums, the exact url it redirects to is not actually a valid url.
You see others reporting the url they are redirected to as being:
http://www.domain.org/wp-login.php/?redirect_to=http%3A%2F%2Fwww.domain.org%2Fwp-admin%2F&reauth=1
But mine displays: http://www.parentsauxassembleesgenerales.org-login.php/?redirect_to=http%3A%2F%2Fwww.parentsauxassembleesgenerales.org%2Fwp-admin%2F&reauth=1
And is therefore missing three characters: “/wp” to be identical to the other bugs I saw reported. Needless to say, I still tried all the fixes recommended elsewhere, namely:
(using FTP, Softaculous, dowload of WP 3.8.1 and 3.8.2 from wordpress.org, and PHPmyAdmin)
1- deactivating, renaming, removing plugins, theme, both plugins and theme
2- adding lines of code to wp-config
3- looking at the database to make sure the site url and home url were the right ones and the same
4- updating key files like wp-login.php with a fresh version straight out of a vanilla install.
5- moving the content and wp-config to a fresh install (only recreated the problem).
I’m sort of confused at Softaculous (wp install script in cPanel) for asking if you want automatic updates, but still enabling the small automatic updates (3.8.1 to 3.8.2 or 3.8.3) even if you don’t check the box for automatic updates. I don’t, and never will, want automatic updates on my wordpress: too many plugins and themes have a lag to the wordpress core deployment schedule. (I now know I can just add a line to wp-config.php, but the Softaculous interface could be clearer about the automatic update deal).
Am now in contact with the hosting service to look at solutions such as emptying webcache, restoring from their own weekly backups, their own diagnosis of the faulty redirect route, etc.
I’m looking for a solution that will do one of the following:
help me know what causes the redirect error so I can target the problem-solving
help me regain access to wp-admin login and the dashboard
I found the issue.
Despite deactivating the plugins, one of the plugins had caused a problem in the DB which remained even when deactivated, removed or renamed. Had to clean up the relevant redirects in the DB with PhpMyAdmin.
The plugin was Velvet Blues Update URLs, which was recommended for a very small move I was doing (moving the dev version of the site up one folder on the server file system).
I hadn't used this plugin before, but it seemed straightforward enough.
Not.
I usually migrate sites using UpDraftPlus with the pro addon for migration, which works fairly well, but felt longer than it needed to be for a one-folder-up move.
Not.
The search and replace feature on UpDraftPlus that covers both for file/folder locations and for urls is without compare, and even for what it was supposed to do, Velvet Blues Update URLs didn't deliver on its promise.