I recently moved a magento install to a new server and a new domain. I updated all the entries in the database with the new domain and path. The admin works fine, indexing works fine, cache management works fine.
However on the front end, the site renders all the way until the first product, and then it stops. The rest of the products don't render, and neither does the footer or any other blocks.
I tried to switch back to the vanilla theme that magento ships with, and it still happens.
The files on the new server are exactly the same (rsynced), and the only difference in the db is the domain and path.
Any ideas?
Edit
If it helps, the currently broken url is http://stiles-store.ddmstaging.com/
It's a fatal error. Turn on developer mode and reload the page - you will see the error message.
You can turn on developer mode by two ways:
1. At backend
2. Change code in index.php from
if (isset($_SERVER['MAGE_IS_DEVELOPER_MODE'])) {
Mage::setIsDeveloperMode(true);
}
to
//if (isset($_SERVER['MAGE_IS_DEVELOPER_MODE'])) {
Mage::setIsDeveloperMode(true);
//}
This error is occurring because you might have specified some images or links of your development machine. So Magento is not able to connect to your local machine/development machine from where it is trying to fetch the components.
Try to check whether you have specified the links of your server on which you are currently running your magento instance .
Hope this helps you
Missing GD support in PHP is the reason for this.
In our case GD support was compiled into PHP 5.3, but when we migrated to the new server with PHP 5.4 the sysadmin forgot to include the now shared GD module.
Unfortunately there were no error messages in the server and Magento logs. Basically this question resp. Jack's last comment saved me a ton of time!
Hope this will help others, as I was searching for the PHP version and product image URLs not rendering.
Related
I know that this question is asked many times before but I'm out of options and none of the answers given on Stackoverflow is helping.
I'm working on migrating a Magento webshop to another server, everything was working fine yesterday until I migrated the app/etc/modules, app/code/community, app/code/local, js and lib folders. Magento just gave me a blank page after that, I removed those folders (keeping the original Magento files) but all the pages are still blank.
My error logs don't give any detail about why the page isn't loading, and removing the # in the index.php for
ini_set('display_errors', 1);
Doesn't work either because the first error that is showing up is a PHP5.3 error because the client runs Magento 1.3.2.1 (fixed by using this tweak: http://spikomoko.wordpress.com/2009/08/19/magento-not-working-on-php-5-3).
Is there anyone with any information because I'm out of options.
Okay, found the answer.
I extracted my lib and js folder from a tar.gz file, this replaced the modified lib/Varien/Object.php with the original one. Causing a blank page error because the errors are disabled in the Magento index.php.
TLDR:
Recently migrated my site to a new host. The header and footer (without CSS) show up, but the pages all show "Page Not Found".
Further Explanation:
I migrated my site (small CakePHP project) to a new host, and did these steps:
And follow this steps:
Migrated every file and folder
Imported the complete database
Changed the database configuration
Checked the folders, everything is set to dirname, and stuff like that, so no problem
Now, when I access the site in the new hosting, it shows page not found, and the CSS are missing. I edited the index.php on app/webroot and added a few echos to see if the flow was ok. If I add an echo, the CSS works (if I add echos in any part of the source, the echo was echo '1';) but still with the "Page Not Found".
What version of CakePHP are you using? If it is 2.x, you need to make sure you have php 5.2.8 or greater.
The other thing to confirm is that mod_rewrite is enabled and working correctly. It sounds like this may be the issue.
Maybe you forgot to copy any of the .htaccess files.
I have just moved a Wordpress install from a remote host to run on my local development machine. On the remote server it's fully functional.
However, on my development box I can only load the homepage. Other URLs just load a standard phpinfo() page with no errors.
Does anyone know what might be causing this?
It sounds like you are using MAMP or WAMP on your dev box, which will load a default vhost showing phpinfo for any page that does not exist.
Inside wordpress, the settings, in the DB, it sounds like you have Url's "hardcoded" like "http://www.mysite.com" which are not working locally because your "dev" Url is something like "http://localhost"
Whenever using a development server, especially with wordpress, you should setup you dev server as close to your production server. This means you should edit your host file to make it so "http://www.mysite.com" actually goes to your development box or localhost. That way you are viewing everything as it will be when it goes to production.
I had this problem as well following the hosting company re-installing an SSL certificate.
I did some searching and really only found this thread which give me the idea there was a 404 error hiding there somewhere so I checked the php_errors.log file (which I found in the root folder of my site in FTP) - opened that in notepad and found many errors such as:
PHP Fatal error: Class 'WordPressHTTPS_Module_phpinfo' not found in /var/www/vhosts/mywebsite.com.au/httpdocs/wp-content/plugins/wordpress-https/lib/Mvied/Plugin.php on line 385
So - indeed a missing file in the wordpress-https plugin.
To correct, I renamed the folder which contained that plugin (eg wp-content/plugins/wordpress-https to wp-content/plugins/wordpress-https-disabled) - effectively disabling the plugin.
This then allowed me to login to the wordpress admin, install the latest version of that plugin - which worked fine and then deleted the old folder (wordpress-https-disabled)
Everyting was good as gold after that
Hope that helps someone :)
open httpd.conf in text editor
Change;
AllowOveride none
To;
AllowOveride All
I had the same challenge when I cloned my remote site locally.
I fixed it by checking the .htaccess file and correcting this line to point to the right project folder:
RewriteRule . /wordpress/index.php [L]
I'm trying to use Dreamweaver with an existing code base (not WP, Drupal, or Joomla!) in a PHP/MySQL site. I continue to receive "Dynamically related files could not be found because of an internal server error." I've been googling all day and have read plenty of WP-specific solutions, including the thread on this site. I've tried all the methods listed, no luck.
Setup Info
MAMP 2.0.1
Mac OS X 10.6.8
Dreamweaver CS 5.5
Site's local address: /Users/myName/Sites/siteName
Testing server address: /Applications/MAMP/htdocs/siteName
Attempted solutions:
1) added library to site root (/Users/myName/Sites/siteName/library)
2) added library to MAMP root (/Applications/MAMP/library)
3) added include path for both locations to applied php.ini listed in phpinfo
4) set Dreamweaver to use Site Root paths instead of page-relative paths
5) switched back to page relative paths
6) Restart MAMP, reset ports in Preferences to 8888/8889, or 80/3306
7) checked site info to make sure paths are correctly defined
When I insert the following code, or any require function with a relative path, live view and preview in browser display empty pages.
<?php require_once('includes/initialize.php'); ?>
I'm incredibly frustrated. I had been using XAMPP and a plain text editor for previous work and never had an issue with relative paths. Any help would be appreciated.
Answering my own question; bad form, I'm aware.
EDIT:
Adding to previous list of attempted solutions:
8) tried designating the server ports as 8888/8889 and defining server route as http://localhost:8889/mySite/, like setting up a Drupal/WP/Joomla! testing environment.
9) Uninstalled/Reinstalled MAMP, Dreamweaver, disabled the out-of-the-box Apache server included with OS X, the redefined the site in Dreamweaver.
Fix attempt 8 led to packet error discussed here. Fix attempt 9, plus error reporting that hadn't been working, but did now:
// Report all PHP errors (see changelog)
error_reporting(E_ALL);
showed that the testing server was using the local definition to refer to dynamically related files and, even though that should work, it wasn't working.
After reinstall, created new site with "Site > Manage Sites" and defined Local Site Folder in "Site" menu and the Server Folder in the "Server" Menu as the same directory. (/Applications/MAMP/htdocs/mySite)
Refer to the Setup info in the OP to see my system variables; this may be specific to any/all settings. But only identical local definition and server definition solved the problem. I've recreated previous settings to be sure, and different local/server definitions don't work.
This error can happen with Dreamweaver and PHP sites if the contents of the included file make additional dynamic calls using PHP syntax that Dreamweaver doesn't recognize. Without seeing the contents of initialize.php, I can't be 100% sure this is the case but I am pretty sure that DW is not able to parse the code there and figure out what files to get for display.
Problem Dynamically related files that I see a lot of people run into:
Dreamweaver is scanning whatever is in you Local Copy, it should be a the full installation of WordPress. If you're working locally, download everything on your "Testing server" to your "Local view" in the Files panel.
If you're working with two sets of files, your local copy and what is in MAMP's htdocs or on your "Testing server" should be nearly identical, except for what you're working on of coarse. That's the problem I see people have.
If you're working in kind of "pho-FTP" environment.
I am building a Wordpress website in Dreamweaver CS5 and am also using MAMP for my PHP/MySQL needs.
The problem is that when I create a new Wordpress site in Dreamweaver (I have an existing Wordpress template), and I open the index.php file, it asks me if I want to discover any other files that are dynamically related to the index.php file. I click "Discover", then I get this error: "Dynamically-related files could not be resolved because of an internal server error."
My MAMP document root is: /Users/Burton/Sites/
In the document root I have a sub-directory called Wordpress where all the Wordpress files (including my theme) are stored
In Dreamweaver I created a new site and here are the settings for it and the server:
Site Name: Test Site
Local Site Folder: /Users/Burton/Sites
Server Name: Local Testing
Connect Using: Local/Network
Server Folder: /Users/Burton/Sites
Web URL: http://localhost:8888/Wordpress
Server Model: PHP MySQL
Testing: On (Make it a test server)
Going to the site via a web browser is fine, I can see the template and everything. I can edit the site in Dreamweaver and see the changes made in the browser, but I want Dreamweaver to discover those other files so I can do Live View in Dreamweaver, but this error is preventing me from doing it.
I've looked at countless tutorials and visited many forums but no one has the answers...
Anybody out there have idea what is causing this?
Thanks!
This happens with DW and WordPress sites because WordPress doesn't use normal include calls but instead does this dynamically based on what the user is doing at the time. DW cannot handle that complexity in design view and chokes on it, displaying the message that you see.
I had this issue, for me it was a mixture of the mysql server address in wp-config.php pointing to localhost when infact the database was on a different domain, and wordpress thinking that it was deployed on the remote / live domain rather than locally.
Changing the database vars (they are at the top of the file, well commented) to point to the right database fixed it.
// ** MySQL settings - You can get this info from your web host ** //
/** The name of the database for WordPress */
define('DB_NAME', 'DATABASENAME');
/** MySQL database username */
define('DB_USER', 'DATABASEUSER');
/** MySQL database password */
define('DB_PASSWORD', 'DATABASEPASSWORD');
/** MySQL hostname */
define('DB_HOST', 'DATABASEADDRESS');
Also, make sure you have, locally, a complete copy of all files in the wordpress install. I installed mine on a remote server via a CGI script, if you do the same then make sure you copy the whole lot to your local site.
The last peice of the puzzle for me was changing the WordPress address (URL) and Site address (URL) inside wp-admin to point to my local copy, relative to Dreamweaver - i.e 192,168.x.xxx/wordpressinstall
(I had to log in on my domain (www.wordpresstest.something) to access the admin tool to do this, then it redirects back to the new address when you save - so make sure you have it correct or it's hard to fix).
Hope this helps anyone else with the same problem.
I found this on this thread
I have come across the same issue and found this thread. The post that explains a bit what we want to hear is post #6 by David_Powers on 01-May-2010 at 05:31.
So to make the problem go away you can go to 'Edit -> Preferences' and disable 'Discover Dynamically-Related Files' while leaving 'Enable Related Files' activated.
Although this fixes the error display I don't quite understand what David_Powers says this function will do and if I actually want it turned on. If someone could help me realize what this option does I would appreciate it.
I found the solution from this link
And verified solution is as follow:
Open your site in Dreamweaver and wait for the message at the top, telling you that there are related files to be discovered. Hit “Discover” and get the error message.
Next login to your local WordPress site via a browser and remember what the current Permalinks are set to (under Settings – Permalinks).
Choose the Default (first option) and hit save.
Go back to Dreamweaver and try the discovery option again. All related files are discovered – hurray!
Head back over to your WordPress site and change the Permalinks back to what they were, then hit save.
I know this is a bit hacky, but until Adobe can figure out a working solution this is as good as it gets, and not really that cumbersome.
It's all about "Permalinks". The problem is the web URL address that you have entered in the test server setup has not the same structure, which WordPress uses.
Open your WordPress Dashboard, under Settings choose Permalinks ( Settings > Permalinks ). You'll see what structure is defined in Wordpress and, maybe, this is a different one, which you have introduced into DW: http://localhost:8888/Wordpress. And your permalinks structure in the WordPress is like http://localhost/yoursite/?p=123.
Check custom structure radio button - http://localhost/sitename and click Save.
Go back to DW site > Manage sites > Edit {your-site}, in the Server tab choose your server, hit the Edit button and put the same structure in the web URL box: http://localhost/sitename.
Local site folder and server folder should be like C:\wamp64\www\sitename\.
I use WAMP and DW on Windows, so do the math yourself.