Please help.
https://www.anantamyoga.co.za
]]>I’ve used Duplicator to copy a WP site from my Dreamhost server tomwarneke.com to a new server instance on Amazon AWS EC2 with WordPress installed.
This is a project for a college course on Cloud Computing that is due soon. For this project, I wanted to try out Duplicator to see if it could be used to clone a new WP site from an existing one.
The EC2 Server is Microsoft Windows Server 2008 R2 with Server express and IIs. MySQL and WordPress were installed using installers provided by Amazon. I deleted the WP content in wwwroot, copied the Duplicator data and installer to the wwwroot directory and ran the Duplicator installer per instructions and allowed it to overwrite the MySQL tables. I deactivated/reactivated plugins, registered Jetpack, etc.
Using MySql Workbench on the new AWS server, it appears that the tables are populated with the data extracted from the source on tomwarneke.com. The new site comes up with the basic format, but with no posts and no about pages, etc. displayed.
Here are the source and new sites to compare:
Source: https://www.tomwarneke.com/
New AWS: https://54.243.190.86
Any assistance is appreciated.
Thank you!
Tom
[email address moderated – this forum does not provide support via email]
https://www.ads-software.com/extend/plugins/duplicator/
]]>I have a serious issue when I try to see my frontend site. There’s a systematic warning message telling that the pages can’t be displayed.
If I refresh the urls, the pages are then correctly displayed.
I then made a cache test and had a timestamps warning message:
Test your cached website by clicking the test button below.
Fetching https://www.rainbowmode.com/ to prime cache: OK
Fetching first copy of https://www.rainbowmode.com/: OK (1.html)
Fetching second copy of https://www.rainbowmode.com/: OK (2.html)
The pages do not match! Timestamps differ or were not found!
Things you can do:
1.Load your homepage in a logged out browser, check the timestamp at the end of the html source. Load the page again and compare the timestamp. Caching is working if the timestamps match.
2.Enable logging on the Debug page here. That should help you track down the problem.
3.You should check Page 1 and Page 2 above for errors. Your local server configuration may not allow your website to access itself.
I followed the above instructions.
1. The timestamps is the same when I reload the page in a logged out browser.
2. I enabled the debug page and if I understand the error log correctly,it seems that WP Super Cache is not enabled, but I guess the settings are nevertheless correctly set…
For example:
09:17:56 / No wp-cache file exists. Must generate a new one.
09:17:58 / In WP Cache Phase 2
09:17:58 / Setting up WordPress actions
09:17:58 / USER AGENT (WordPress/3.4.1; https://www.rainbowmode.com) rejected. Not Caching
09:18:01 / supercache dir: /homez.547/rainbowm/www/wp-content/cache/supercache/www.rainbowmode.com/
09:18:01 / No wp-cache file exists. Must generate a new one.
09:18:02 / In WP Cache Phase 2
09:18:02 / Setting up WordPress actions
09:18:02 / USER AGENT (WordPress/3.4.1; https://www.rainbowmode.com) rejected. Not Caching
09:18:06 / supercache dir: /homez.547/rainbowm/www/wp-content/cache/supercache/www.rainbowmode.com/
09:18:06 / No wp-cache file exists. Must generate a new one.
09:18:07 / In WP Cache Phase 2
09:18:07 / Setting up WordPress actions
09:18:07 / USER AGENT (WordPress/3.4.1; https://www.rainbowmode.com) rejected. Not Caching
or
09:40:05 /artists/revides/ supercache dir: /homez.547/rainbowm/www/wp-content/cache/supercache/www.rainbowmode.com/artists/revides/
09:40:05 /artists/revides/ Cookie detected: wordpress_logged_in_a6b4a61ec0ee6f6d25b6ab7a51911ab2
09:40:05 /artists/revides/ No wp-cache file exists. Must generate a new one.
09:40:06 /artists/revides/ Cookie detected: wordpress_logged_in_a6b4a61ec0ee6f6d25b6ab7a51911ab2
09:40:06 /artists/revides/ In WP Cache Phase 2
09:40:06 /artists/revides/ Setting up WordPress actions
09:40:06 /artists/revides/ Created output buffer
09:40:06 /artists/revides/ Cookie detected: wordpress_logged_in_a6b4a61ec0ee6f6d25b6ab7a51911ab2
09:40:09 /artists/revides/ Output buffer callback
09:40:09 /artists/revides/ Supercache disabled: GET or feed detected or disabled by config.
09:40:09 /artists/revides/ Cookie detected: wordpress_logged_in_a6b4a61ec0ee6f6d25b6ab7a51911ab2
09:40:09 /artists/revides/ Not caching for known user.
09:40:09 /artists/revides/ Cache is not enabled. Sending buffer to browser.
09:40:09 /artists/revides/ wp_cache_shutdown_callback: collecting meta data.
09:40:09 /artists/revides/ Did not write meta file: wp-cache-6532144f2d1bbe26e4b40de45386f8e5.meta ** *1* *1*
09:40:11 /artists/revides/index.php?wpsc_ajax_action=get_cart Cookie detected: wordpress_logged_in_a6b4a61ec0ee6f6d25b6ab7a51911ab2
09:40:11 /artists/revides/index.php?wpsc_ajax_action=get_cart In WP Cache Phase 2
09:40:11 /artists/revides/index.php?wpsc_ajax_action=get_cart Setting up WordPress actions
09:40:11 /artists/revides/index.php?wpsc_ajax_action=get_cart Not caching POST request.
3. I don’t see any error on Page 1 & 2.
This is extremely problematic because the all website seems to be offline if I don’t refresh every link to generate a cached file, and I’m not sure anyone else will do this but will leave the site instead…
Is the issue linked with the timestamps? Am I doing something wrong?
I have no idea how to fix this regarding the procedure I followed.
I’ll try to preload the pages once again, but I don’t know what else I can do, and I can’t afford to have the site “offline”.
Any help is really welcome…
Thanks forward!
https://www.ads-software.com/extend/plugins/wp-super-cache/
]]>So I’m using the Creativix Theme for my website and no matter what I do the top navigation menu will not display my pages. I’ve searched the forums and I’ve re-assigned the menu in theme locations and I’m still having this problem. Any help would be greatly appreciated.
Here’s the site: https://apcenergy.com/
Matt
]]>I have taken the following steps, but still it does not work:
1. Verified that PHP 5 is running.
2. Used Sequel Pro to verify that the MySQL database is being populated with the various blog entries.
3. Directory Stuff:
3a. Created a new folder only for WordPress /Library/WebServer/Documents/blog
3b. Moved all of the WP filed into the /Library/WebServer/Documents/blog folder
3c. From the WP folder, removed the index.php file back up to the same directory containing the index.html file e.g., /Library/WebServer/Documents/
3d. Modified the /etc/apache2/httpd.conf file to have apache2 to point to index.html index.htm and index.php instead of the default setting which is only index.html
3e. Modified the WP admin control panel so that the WP directory is https://hostname/blog/
3f. Verified that the MySQL settings for the wordpress database have the site URL set at https://hostname
What is really strange is that the wp admin control panel is accessible, and also the dashboard for a test user.
It is simply that when one tries to “visit site” or “view page” it always takes me back to the old index.html file.
I though I would see if anyone has any ideas before I tear the entire thing down and start again.
]]>