We are developing Wordpress sites and due to some issues with some plugins once the domain is changed (from dev.domain.com to www.domain.com), we have been using a practice of editing host files in house so that we can develop the site on the www.domain.com domain.
This solution works fine for us in house, however when a client wishes to see their site in development we have to walk them through the editing of their host files to see the development site and then back so they can see their live site.
Does anyone have a better idea or solution. Is there a way to make this work at the Apache level? Maybe a Chrome app? It needs to be super simple and automated (scripted) if possible.
Thanks
You could create an VPN connection to your "house" so that the fake www.domain.com will be avaible for them.
So, the issue is that some plugins think they're on www (or will only behave correctly on www)?
Then quite possibly your best quick bet is a Chrome/Firefox extension, although obviously that does require the client to have them installed.
I'd recommend looking at HostAdmin for Chrome and/or fire-hostadmin for Firefox. These should allow you to amend the hosts without too much hassle or direct editing of protected system files.
It is always worth noting that, depending on the client's computer's security, they may run into potential read-only issues (I believe SpyBot Search & Destroy and similar tools lock the hosts file by default).
Related
I'm facing a problem with the following website: https://www.rhythmandstrums.ie/
When I open the "www" version of it: https://www.rhythmandstrums.ie/ I get a bugged website, failing to open stylesheets and possibly other file sources, whereas if I open the website without the "www", everything works as expected: https://rhythmandstrums.ie/
Some considerations:
This website is hosted in a Wordpress Multisite, so it shares the same configuration files as other websites, none of the other websites have this issue. So I was wondering if this could be a problem with redirection, although, again, none of the other websites have this problem and they share the same config files (including server block settings and such, it is in nginx).
I have checked the DNS values and nameservers and everything looks fine (I took base from all the other websites that were set up in the same way, I can post a screenshot if it might be of help).
This error also seems to happen in the Wordpress backend, with the admin dashboard not being able to load parts of plugins, it seems like it is looking where it doesn't exist.
I have replaced instances of the www version of the url in the database, as I do with other websites as well, but that didn't seem to fix the issue.
I have cleared cache a few times (both in the cache plugin and manually in the nginx server - manually deleting the contents of the cache folder), and since this has been going for a long time, I don't know if this is cache related, but any suggestion is highly appreciated. Again, all the configs, included the cache plugin settings are the same for all the other websites in the network, which none are having this issue.
If I inspect the console when I'm accessing both versions of the website, www and non-www it seems like it's trying to pull information from different locations, but I can't figure out why it's doing that.
Guys, I hope this was not confusing, but let me know if you you would like to see screenshots or other info that might be relevant. Thanks so much in advance, I really appreciate it.
I have built my wordpress/woocommerce and hosted it on Localhost via WAMP.
Since day one, before I had loaded any plugins etc and only had the wordpress CMS installed, it has ran very, very slow.
I have been advised that it should be no where near as slow as it is and could be a variety of reasons for this such as bad coding.
I am very new to web design etc and was wondering if someone would be able to advise as to how to check what might be slowing things down?
I have installed jquery monitor and it shows a few different things but all are plugins which are relatively new and the problem has been there since day one...
I have been looking for a free host to try on but my website exceeds the size as it is at 1.6gb which people have said could be the problem, however the problem as I have mentioned has been there since day one with only the basic CMS shell and no uploads.
My comuter is also relatively fast and I have no issues with how it runs i general.
Any help would be much appreciated.
Do you use http://localhost for accessing the website and "localhost" as MySQL host? If yes, try accessing the website through http://127.0.0.1 and 127.0.0.1 in your wp-config.php for your MySQL host. Depending upon your Windows version and network settings it is possible that your DNS resolution fails.
Do you have Antivirus solutions enabled? Try to disable them temporarily and check if the problem still exists.
Check with tools like Wireshark and procmon which of the components (webserver, network, client) take how long for processing the HTTP requests.
If all directories hosted on your local server are slow then this means your WAMP is the one causing the issue.
Try backing up everything and resolve this by following this instructions here
https://www.devside.net/wamp-server/wamp-is-running-very-slow
This worked for me.
I recently pointed my 1&1 registered domain, masonsmn.com, away from justhost where I had a wordpress site built toward my new site constructed using squarespace.
I would like to view a few pages of the old site as they were previously (i.e. I messed up. In hindsight a few screenshots then would have been a good idea).
Does anyone know how I can access those wordpress pages at this point?
Thanks,
You can add a hosts entry to your computer to force it to go to the old IP address. See google for instructions for your operating system. Don't forget to remove it later! :-)
The old site is on justhost. Do you still use them for hosting? If so, just download your old wordpress files via ftp. If you already cancelled your hosting, but it wasn't long ago, they may have your files backed up still. If this is the case I would give them a call and see what they can do.
In a wordpress installation we want to have our main site, and a staging site separated and different. Where in the admin interface you separate your staging area?
Let's say:
for production you will have: http://www.yourdomain.com/
but for staging we want to have: http://www.yourdomain.com/staging
Staging is the website that will be in production next.
Any ideas?
With Wordpress 3.0+ you might be able to create a network of sites or install multiple sites with an older version of Wordpress. The catch is I don't know of an easy way of moving the staging to production. I'm not entirely sure that will do what you want, but you may want to look into it.
Personally I'd think you'd probably be better off keeping your staging and production sites on 2 different servers and just do a copy over when you move to production.
I don't know of any instant, simple answers, but have you seen this article in the Wordpress support forum? It has some informed discussion and at-least partial solutions:
http://wordpress.org/support/topic/one-wpseveral-servers
If your staging site doesn't need any database modification, or custom forms/widgets for the backend, you can create a new theme, and test it in the preview mode. When done, you can switch the theme to the new one!
I'm developing a website on EC2 and have the development and live site hosted on the same server (for $'s sake).
What I'm encountering is caching conflicts. Specifically on the dev site I have things that are not intended to be seen by the public yet but because it seems that both sites are using the same APC cache the entries are conflicting, and so the public is seeing things it really shouldn't yet.
The dev environment is a complete copy of the live site just checked out from subversion.
Both sites are available on different domains if it helps tailor the answer.
Any suggestions on how to make sure this doesn't happen?
I've drilled down into the AuthCache code and found that there are many things that can cause a page not to get cached. Among them is isset($_COOKIE['nocache']). This means that I can set $_COOKIE['nocache'] on login in my own module when the request is being performed on the on the dev site.