About JLHC

JLHC · ‎05-20-2015

I agree with @theMageComp that invalid file permissions can indeed result in the 403 error. Try applying the correct file permissions for all files and directories (check with your hosting provider on their recommended file permissions) and see if the files are accessible.

JLHC · ‎05-18-2015

It looks like there's a duplicate row in your MySQL database. I suggest that you move the database over again and make sure to import it into a fresh and empty database.

JLHC · ‎05-14-2015

Try seeing if the file maintenance.flag exist in your Magento root directory. If you see this file, remove it and the error will go away.

JLHC · ‎05-12-2015

I've removed your email address to prevent a huge amount of unsolicited emails from going your way. Anyway if you have any questions for any providers including us, please do contact the provider directly.

JLHC · ‎05-09-2015

Taking a look at that VPS, your biggest bottleneck will be the low amount of RAM as 768MB is simply not enough to power even a small Magento store, let alone two stores with thousands of products. The hosting control panel (cPanel/WHM) itself would already consume quite a sizable portion of your total RAM so there will be not enough of memory for your Magento stores. With the size of your store and number of products, I'll suggest at least 2GB of RAM for optimal performance.

JLHC · ‎05-09-2015

I disagree that you will need a dedicated server just for Magento store to perform well. What is the specification of your VPS? Is it managed or unmanaged? Is it properly tuned and optimized? It is very important that you have a good VPS or server with decent specifications and are properly tuned and optimized for Magento. A lower end VPS which is untuned and unoptimized will perform even slower than shared hosting services which are properly optimized for Magento.

JLHC · ‎05-09-2015

If you changed the "max_execution_time" in the .htaccess file and it is still not reflected, maybe there are some other configurations which are causing the timeout. Anyway I suggest that you consider using an alternative backup solution instead as Magento's built-in backup is not that good anyway due to a few reasons:- 1. It always reset file permissions wrongly to insecure permissions like 666 and 777 after a backup. 2. It doesn't backup everything. 3. While backing up, it takes up resources of your account if you are in shared hosting which can put a strain on your website.

JLHC · ‎05-06-2015

Do you see the following codes in your /app/etc/local.xml file? <cache> <backend>database</backend> </cache>

JLHC · ‎05-06-2015

If you mean session storage, you are given a choice to choose either to use the File System or Database during installation. If you selected Database and want to change it to File System now, open your /app/etc/local.xml file and search for:- <session_save><![CDATA[db]]></session_save> Replace it with:- <session_save><![CDATA[files]]></session_save>

JLHC · ‎05-05-2015

I believe the license is for a single store regardless on the amount of servers running in the backend. Your best bet is to contact Enterprise Edition's Sales Team for confirmation:- http://enterprise.magento.com/explore/contact-sales

JLHC · ‎05-05-2015

Try checking to see if your file permissions are messed up, which can happen after a download or upgrade from Magento Connect Manager and also after taking a backup within Magento. Under most hosting environments, the file permission for all files should be set to 644 and all directories to 755. If you are unsure on the ideal file permissions for your server, do contact your hosting provider.

JLHC · ‎05-05-2015

This is not the default behavior for Magento. I suspect that there are redirect rules in your .htaccess file. Try looking into it and remove those rules.

JLHC · ‎05-05-2015

As your website is highly customized, I suspect one of the customization broke something. How is your Disk Space usage like? Servers with full disk space will also result in the inability to login but it should throw a completely different error. Anyway Magento 1.4.x is simply too old and too many things can go wrong. It is also definitely not compatible with PHP 5.4. You should definitely have a plan in place to upgrade to newer versions.

JLHC · ‎05-05-2015

Your best bet is to restore the database from a working backup before the corruption. Is there any reason why MySQL is not properly tuned before you even install Magento? Are you on shared hosting or your own server? Is it managed or unmanaged?

JLHC · ‎04-19-2015

Your installation may have been patched with SUPEE-1533 which is why the patch failed. Anyway please do open a new thread if you need further assistance about this as it is unrelated to this topic.

JLHC · ‎04-19-2015

Yes, you still need to apply the patches that are applicable for version 1.9.1:- https://www.magentocommerce.com/products/downloads/magento/ Click on "Select your format" and you can see if the patch is required for your version.

JLHC · ‎04-19-2015

There are multiple patches where some are application from 1.4.x all the way to 1.9.x while some are for certain versions only. You can view and download the patches here:- https://www.magentocommerce.com/products/downloads/magento/ Click on "Select your format" and you can see if the patch is required for your version. The current critical patch is SUPEE-5344 which "Addresses a potential remote code execution exploit" and it is applicable for Magento version 1.4.x all the way to 1.9.x. After downloading the patch, you will need SSH / Shell Access* to implement them:- ==== Please upload the patch into your Magento root directory and run the appropriate SSH command: For patch files with the file extension .sh: sh patch_file_name.sh Example: sh PATCH_SUPEE-1868_CE_1.7.0.2_v1.sh For patch files with the file extension .patch: patch –p0 < patch_file_name.patch Once that is done, refresh the cache in the Admin under "System > Cache Management" so that the changes will be reflected. We highly recommend you test all patches in a test environment before taking them live. ==== * SSH / Shell Access SSH / Shell Access is usually not enabled by default for shared hosting accounts due to security reasons. You can contact your hosting provider to enable it for you (most will require a Photo ID while some may charge a small fee). If your hosting provider refuse to enable it for you, try asking if they can run the above command for you (make sure you provide them the correct command with the proper path to your Magento root directory).

JLHC · ‎04-19-2015

Try checking if your file permissions are set correctly, especially for the "/downloader" directory. For a server with SuPHP / SuExec, all files should be set to 644 and all directories to 755. Otherwise some of the directories will need to be set to 666 and 777 (which can be insecure). You may need to contact your hosting provider to know the correct file permissions to use.

JLHC · ‎04-19-2015

@strobotron wrote: it's a relatively inexpensive provider with shared hosting -- they do not provide SSH access due to security concerns (their words, not mine) -- and since Magento is not their product ... well, let's just say i needed to find another solution thanks for the responses everyone! Well if they can't allow SSH access for you, they should at least be able to execute the command for you? Anyway most providers will be able to provide SSH and to mitigate the security risk, you usually just need to provide a valid Photo ID.

JLHC · ‎04-17-2015

Can you have your hosting provider execute the patch command for you instead? Did they let you know the reason why they do not allow SSH access?

JLHC · ‎04-17-2015

There are three ways where you can go about this:- 1. The first way is to set a host entry in your computer to point the domain to the IP address of the new server when you want to access it and remove the host entry when you want to access the old server. This is not ideal and not really recommended if you want to switch back and forth or see the two stores side by side. 2. The second way is to change your Magento Base URL to the IP address of the new server (for example: http://1.1.1.1/) while you are developing the store. You can change the Base URL to your correct domain when you are ready to go live. 3. The third way is to create a subdomain like "dev.yourdomain.com" and add it as a Parked Domain in your cPanel where it will share the same document root as the main domain (so you will not need to move files, paths, etc). You can then change the Magento base URL to this subdomain while you are developing the store and change it to your correct domain when you are ready to go live.

JLHC · ‎04-17-2015

What sort of hosting platform are you under? Is the site live now or still under development?

JLHC · ‎04-17-2015

Optimizing the server should be more important than just upgrading it with more resources but without knowing your usage, it can be hard to tell. Try running a GTmetrix on your website and see whether your contents are slowing things down?

JLHC · ‎04-12-2015

You did not mention the amount of RAM for your server? Anyway firstly, check if the server itself is overloaded or if it is coping fine. Do you have things APC, Memcached, Redis, Varnish, etc installed and tuned in your server? Is the server managed by your hosting provider, a third-party or do you manage the server yourself?

JLHC · ‎04-10-2015

It can be due to a few reasons, including file permissions, JavaScript and yes extensions as well. Did you install any new extensions recently? Have you tried this with another web browser and make sure JavaScript is not disabled?

JLHC · ‎04-07-2015

Did you contact the Magento Connect team at this link? http://www.magentocommerce.com/magento-connect/feedback/

JLHC · ‎04-07-2015

Is this a fresh installation? Did you do anything before the error happened?

JLHC · ‎04-05-2015

Is this a fresh installation? What version of Magento are you running? Do you see the problem every time you login? Something is turning on output buffering: http://php.net/manual/en/function.ob-start.php You may be getting some other errors like the "out of memory" but as buffering is on, the error may not be shown.

JLHC · ‎04-05-2015

Try checking if your file permissions are set correctly. If your hosting server is using SuPHP or SuExec, set all files to 644 and all directories to 755. If the server doesn't use SuPHP or SuExec, you may need to set some of those files and directories to 666 and 777 like /media and /var.

JLHC · ‎04-05-2015

Just to add that Magento should work fine with MySQL 5.5 while Magento 2 will strictly require MySQL 5.6 and above.

Re: Installation problem on 1und1 Hosting

Re: error after moving site to other hosting but s...

Re: Error 503 - Service Temporarily Unavailable

Re: Is this Cloud VPS robust enough for 1400 trans...

Re: Is this Cloud VPS robust enough for 1400 trans...

Re: Magento store very sluggish

Re: Magento media and system backups fail

Re: Table Core_Cache increasing rapidly

Re: Table Core_Cache increasing rapidly

Re: Magento EE and load balancer

Re: error 503

Re: www / non www

Re: Customer login issues (frontend) on website

Re: Corrupted database?

Re: Patches for New CE 1.9.1 Install

Re: Latest CE release & patching

Re: Patches for New CE 1.9.1 Install

Re: Magento Connect... this error message appears

Re: install security patch without access to SSH o...

Re: install security patch without access to SSH o...

Re: access new Magento install using the same doma...

Re: Site taking up to 20seconds to load!

Re: Time to first byte slow on multi-domain setup

Re: Time to first byte slow on multi-domain setup

Re: Magento not responding after category save

Re: No reply from magento

Re: Error on admin panel

Re: Error on admin panel

Re: After Installation of Test Site Can't Add Prod...

Re: Magneto compatibility with MYSQL