I am moving a magento store from mydomaintest.com to mydomain.com.
When I say move, in this instance, we simply used the Cpanel to Modify Account and changed the Domain Name from mydomaintest.com to mydomain.com.
Then using the advice found in forums I used PHPMyAdmin to update the Magento Core Config table to the new BaseURL for both Secure and Unsecure url's.
After doing this I deleted all files in /var/cache.
Trying to access the site by domain name or IP is providing the following error:
Fatal error: require_once() [function.require]: Failed opening required '/home/mydomain/public_html/errors/report.php' (include_path='/home/mydomain/public_html/app/code/local:/home/mydomain/public_html/app/code/community:/home/mydomain/public_html/app/code/core:/home/mydomain/public_html/lib:.:/usr/lib/php:/usr/local/lib/php') in /home/mydomain/public_html/app/Mage.php on line 847
Please help, we are trying to move live today and can't seem to figure this one out.
Thanks!
John
Go to System > Index management and Reindex data as it also contain the url rewrites. Also be sure to check System > Cache Management (some versions still have that) and flush all cache as var/cache is not the only caching location. The zend components save their cache in the tmp folder.
I had this issue with Magento running with Apache2 on Ubuntu 14.10
Make sure that MySQL module for PHP is install:
dpkg --list | grep php5-mysql
If it is not listed, you need to install it:
sudo apt-get install php5-mysql
Then restart Apache:
sudo service apache2 restart
In our case we get this message because someone deleted the "error" folder - the site works fine until an error happens.
Once we restored the folder (and make sure PHP can access it), we see the normal Magento error page.
If you don't have the folder you can download Magento and extract it from the archive.
Related
I'm trying to install ultimo on my copy of Magento 2. The theme is appearing in the content configuration panel but it doesn't seem to apply the theme and I'm getting a large number of console errors such as those in the following screenshot:
This may be because I have been unable to enable the theme properly as I'm having some issues with the SSH.
When I try to enter the following command
bin/magento module:enable Infortis_Base Infortis_Brands Infortis_Cgen Infortis_Dataporter Infortis_Infortis Infortis_Ultimo Infortis_UltraMegamenu Infortis_UltraSlideshow
It keeps coming up with messages such as:
-bash: bin/magento: No such file or directory
I should probably also mention that on this occasion the server where the files are stored is being run by a third party and controlled through a Plesk panel.
If anyone could clarify what it is that I'm doing wrong here I would greatly appreciate it.
Thanks
verify that you are executing the command from the right location, maybe you did not change the directory to DocRoot where magento is installed:
# cd /var/www/vhosts/domain_name/httpdocs/
After that execute the command query once again
go to your magento root via cd command
then fire below command
php bin/magento module:enable Infortis_Base Infortis_Brands Infortis_Cgen Infortis_Dataporter Infortis_Infortis Infortis_Ultimo Infortis_UltraMegamenu Infortis_UltraSlideshow
if still you face issue this may be permission issue then you can reset file/folder permission via below
https://magento.stackexchange.com/questions/91870/magento-2-folder-file-permissions
Thank you to everyone who posted. It was actually a combination of the answers provided by other contributors plus something from my server provider.
I had to CD into httpdocs (the magento installation folder) and enter the below command
/opt/plesk/php/7.0/bin/php bin/magento module:enable Infortis_Base Infortis_Brands Infortis_Cgen Infortis_Dataporter Infortis_Infortis Infortis_Ultimo Infortis_UltraMegamenu Infortis_UltraSlideshow
Then run 'setup:upgrade', this seems to have fixed the issue and I can now use Ultimo.
Today when i logged into my magento store admin, it shown a new critical message like
Critical Reminder: Download and install Magento security patches. Download now.
Then i download SUPEE-5344 and SUPEE-1533 from https://www.magentocommerce.com/products/downloads/magento.
Please tell me how can i apply these patch files to my magento store.
Thank You!
Applying SUPEE-5344 and SUPEE-1533 Magento patches via FTP/sFTP or FileManager / File Upload without SSH
Refer Link: http://magentary.com/kb/apply-supee-5344-and-supee-1533-without-ssh/
You can test whether Magento is safe from vulnerable for security point of view see link: https://shoplift.byte.nl/ and enter your URL.
You should have a look at the official documentation on applying patches
But in short.
Download the patch from the Magento site,
Transfer the patch to you Magento installation root directory,
Call sh patch-file-name.sh and you should see the message Patch was applied/reverted successfully.,
You may need to revert permissions after the process and also make sure you download the right patch for the version of Magento you have in place.
for SSL use putty client software and use it to access SSL.
Go to your website hosted directory and type the
above command and yout patch get applied/reverted successfully.
Steps To Run Security Patche File in magento.
1 First download security error patche file from magento community .
2 Download files move it into root folder in magento.
3 Create a php file in root directory of magento for run patche files.
4 Rename Security patches files according to you.
Final Step Open Php file and add these function in php
<?php
print("<PRE>");
passthru("bash patch-1.sh");
print("</PRE>");
//patch-1.sh define the name of download security patch file name .
?>
First download .sh patch files and move to your document root (magento root folder). Then connect to ssh and go to your document root folder.
run this command.
sh patch-file-name.sh
A message such as the following displays to confirm the patch installed successfully:
Patch was applied/reverted successfully.
Delete cache and session.
rm -rf var/cache var/session
Now you may need to reassign ownership again. Based on your group name command. Generally there are two groups www-data or apache. If you have www-data then run this command
chown -R www-data .
For apache use this.
chown -R apache
I installed Joomla 3.1.1 Stable on a Centos system.
I can access it, browse through it's admin backend and frontend, but I found in the Extension Manager/Warnings that "The PHP temporary directory is not set"
I went on google and found a fix: I created a php.ini file where I completed this line:
upload_tmp_dir = var/www/html/joomla/tmp
I did that because that is the location where I installed joomla (var/www/html/joomla/)
The fix I found online gave some other location for this folder, it was something with the home/accountname/public_html/... , but I do not have joomla installed in any accounts, it is installed in the "public": var/www/html folder.
I am asking what am I doing wrong because even after doing this, the warning stays the same:
"The PHP temporary directory is not set"
How can I fix this?
I set up the permissions for the entire joomla folder to 40777, and then to the inner folders and files so I would avoid a permission conflict. I then disabled the FTP from Global Settings (before doing this I was receiving a lot more errors when trying to upload anything)
I seriously thought that installing joomla on Centos would not give me so many headaches.
I need to install an extension in joomla (for a template) and I have an error that says nothing to me:"-1 - An error has occurred." - "Copy file failed" so I try to fix any warnings/errors that may cause this before giving up.
The fixes found online about this error (Copy file failed) refer to joomla 1.5 - 1.6. How is it possible that I still get it in version 3.1 ? It is rather absurd.
Any help would be appreciated.
Try to set it via .htaccess file, just add this:
php_value upload_tmp_dir /var/www/html/joomla/tmp
It started working after I changed permissions to ALL subfolders located in var/www/html/joomla
I will reset those permissions after I finish with configuring and customizing the website.
But for now, that was my solution.
-di3sel - the upload_tmp_dir was set up correctly in the php.ini
Thank you both, but my problem seems to be solved now.
I have created a local copy of my remote store (Magento Community 1.6.2.0) using WampServer 2.2E:
Cleared entire Magento cache on remote site
exported remote MySql database using phpMyAdmin
tar'd up the entire remote public_html folder and downloaded to local PC
Recreated directory structure locally under C:\wamp\www\
created a new database locally (I'm using WAMPserver) with appropriate user/pass/DBname according to /app/etc/local.xml -- note: dbase host in local.xml is "localhost"
imported database with no errors
modified mage_core_config_data table's baseurl variables to both point to http://www.localhost.com/
modified local .htaccess to prevent configuration that would result in crashing as well as to modify the rewrite rule that does the 301 redirect for domain.com to www.domain.com (I changed domain.com to be localhost.com).
deleted everything in var/cache, var/session, var/tmp, and the system /tmp folder, as suggested in another Q&A
verified that WAMP has curl PHP extension enabled
So now everything loads except for the admin panel. When I go to http://localhost.com/index.php/admin and log in, the error is:
( ! ) SCREAM: Error suppression ignored for
( ! ) Fatal error: Call to undefined function curl_setopt() in C:\wamp\www\includes\src\Varien_Http_Adapter_Curl.php on line 52
I assume that curl_setopt() is defined in the curl library, and that extension is enabled in WAMPserver.. anyone know what's going on with this?
I just realized that my php version is 5.4.3. Wampserver.com offers a 2.2E package with 5.3.13, but that also doesn't work.
I got this to work only by finally trying wampserver 2.2D, which has php version 5.3.10. I used the 64-bit installer -- didn't try the 32-bit but I assume it will work.. This information is notably absent from the magentocommerce.com wiki entry on setting up Magento with WampServer.
New problem is now no page other than the home page loads (404 not found happens for all product pages and categories). This is solved by ensuring that Apache rewrites are enabled (wampserver menu->apache->apache modules->rewrite_module)
Fatal error: Call to undefined function curl_setopt()
This error mean that php5-curl is not available/activated on your system. You should be able to activate it through the wamp configuration panel.
For linux users, install php5-curl through your packet manager.
When I try to install any component, specifically my mtwMigrator component, I receive the following error:
* Warning! Failed to move file.
This is on a fresh install, with FTP Layer turned off, with default content installed, Joomla 1.5.14, latest PHP and my_SQL versions, Legacy mode turned on.
A very common cause of this error is due to file permissions. Joomla must be able to copy the files from your component into the components and administrator/components directories. If the system user the webserver runs as does not have write permissions to these folders, it will not be able to copy the files over.
The FTP layer is there to get around this issue. With the FTP layer on, you upload the component to the server first, then it is FTP'ed from the temporary directory to localhost. For this to work, the FTP user you specify must have permission to write to the components and administrator/components folders.
I had a similar problem when moving between machines (I know you said it was a fresh install - but someone might find this helpful). Ensure the $tmp_path entry in joomla\configuration.php is pointing to a valid directory. Mine wasn't.
In your Joomla backend, on the top menu, go to Help >> System Info >> Directory Permission and ensure that that are writable otherwise you don't want to have to change the folders to 777 and back again each time you install an extension.
In addition to this, you can mass chmod folders and files using Akeeba Admin Tools.
You mgiht also want to update to the latest Joomla 1.5 version (1.5.26)
The most ideal permission for Joomla directories is 755. There are cases when mod_suphp is not installed that the permission problem would occur.
Make sure that mod_suphp is installed and loaded by checking your php info e.g. and running this on your browser. If mod_suphp is not installed, then you will need help from your hosting provider to install this for you.
Normally, all directerories should have 755 (rwxr-xr-x) and all files 644 (rw-r--r--). If you want to set the most directories to not-writetable, you will need at least the directories listed in Help > System info > Directory Permissions. (Here you can also check which directories need to be changed, as non-writetable directories are shown in red.)
In some shared hosting environments, 755 / 644 isn't enough, as the owner of the file is not the (Web)Server User, but the FTP-User ... so either change it to 777 / 666 (not recommended, as you allow others to write your files), or get your FTP layer to work.
Another try: Joomla! does not work yet with the recent PHP 5.3. Can you use PHP 5.2? (Similar Problem in the Joomla Forum)