I've setup VPS (webserver) on Centos 7 (Centos Web Panel 7) and I can't upload larger .zip archive (smaller archive works).
When uploading, it completes but the .zip archive vanishes.
Same results from root login and user panel login.
This is what I have:
PHP Version 7.3.6
Zip enabled
Zip version 1.15.4
Libzip headers version 1.5.1
Libzip library version 1.5.1
I am trying to upload 120MB zip archive containing 46000 files.
What is the problem here?
Thanks
I've only changed this in my global php.ini:
upload_max_filesize = 2000M
max_file_uploads = 100000
Related
I tried to install Typo 3 11.5 from zip and Composer and the result was 404 to Backend.
In log files, there is no information. I tried some topics with config in files but I don't have these config files.
Next, I tried to install 10.4 via composer and it failed:
Script typo3cms install:fixfolderstructure handling the
typo3-cms-scripts event returned with error code 255 Script
#typo3-cms-scripts was called via post-autoload-dump
in:
\public\typo3\sysext\core\Classes\Database\Driver\PDOStatement.php on
line 67
I followed the Installation Guide from the website every time.
I am not sure you can help me with this pure "error log" above but:
Does someone install Typo3 successfully last time, could you provide some information how you did it?
P.S. Every .zip pckage has public folder missing and it doesn't create after installation complete.
But the installation guide require public folder:
cd public
mklink /d typo3_src ..\typo3_src-10.4.x
mklink /d typo3 typo3_src\typo3
mklink index.php typo3_src\index.php
I cannot do this step. Source:
https://docs.typo3.org/m/typo3/guide-installation/10.4/en-us/QuickInstall/GetAndUnpack/Index.html
Is mod rewrite activated for your hosting environment?
Starting with TYPO3 11 the backend uses proper routing which also needs mod_rewrite (or similar configuration for nginx) in the Backend.
Currently we are working in a project that must be developed in an environment behind a firewall and we don't have access to internet so, we are not able to install de pods in the iOS project.
We have the opportunity to use Artifactory to cache the pods, but currently it only works for the ones that are stored in github, so for example GooglePlace, GoogleMaps pods cannot be installed as they are distributed as tgz.
Do you know a way to install those pods in Artifactory? As we have seen, in order to publish them in a Cocoapod repository we will need to
a) download the .tgz
b) create a specfile in groovy, cause at least we are not able to make use of the .json podspec of google to let it index and recognize the pod.
Maybe the problem is that we are not using the json file properly. As far as we know, the spec file has to be inside the tgz file, but it didn't recognize the file as I mention before.
We were able to make it work. It was just a problem with the tar.gz file. The steps we follow was in a osx:
Download the json spec file with curl
Download the tar.gz source that we can locate in the json spec the pod file
Uncompress the tar.gz
Add the json spec file to the root folder of the uncompressed data
Compress with the gnu-tar (that can be installed with brew) the file, with tar.gz extension
Upload to artifactory
With those steps, and using jfrog repo-art plugin we can use the pods without internet connection
I am trying to install the SUPEE 6285 on Magento v 1.9.0.1
We do not have a SSH to our server. When I try to Method 1 found on magecomp.com/blog/how-to-install-magento-security-patches/ I get a blank page when I run the patch on the browser.
After looking at the FAQS I see that I should have an install.php file under app/code/core/Mage/Install/Controller/Router/Install.php however I don't have a Router directory.
Any advise on how to install the patch?
First solution (recommended):
Use Magento connect and upgrade your store to the latest Magento version by check for upgrades. The latest version contains this security patch (SUPEE 6285) and another features all together.
Second Solution (Install patch manually):
Download SUPEE 6285 - v 1.9.0.1_v2
Use an FTP client to upload the specific patch to the root of your Magento folder.
Create a PHP file called applypatch.php that will run the patch for you.
upload it to the root of your Magento folder. Make sure to use the right patch name here.
<?php
print("<PRE>");
passthru("/bin/bash PATCH_SUPEE-6285_CE_1.9.0.1_v2.sh");
print("</PRE>");
?>
Visit the file at http://yourdomain.com/applypatch.php, and check if the output looks as expected.
Unfortunately, there's no 'easy' way to install these patches without shell access, but there's two ways to do it.
Install patch through PHP
Use an FTP client to upload the specific patch to the root of your Magento folder.
Create a PHP file called magentopatch.php that will run the patch for you, and upload it to the root of your Magento folder. Make sure to use the right patch name here, if you don't use the patch for version 1.8.x-1.9.x
<?php
print("<PRE>");
passthru("/bin/bash PATCH_SUPEE-5344_CE_1.8.0.0_v1.sh");
print("</PRE>");
?>
Visit the file at http://your.domain.com/magentopatch.php, and check if the output looks as expected.
Install patch manually
The .sh file contains a 'DIFF' patch. These show what lines were removed and added. While I don't advise it, you should be able to manually download the files through FTP, and edit these files in your editor of choice, and then reupload them again through FTP.
The format isn't too hard to interpret, so you can do this for all the files and shouldn't take more then a few minutes.
i need to upgrade my magento store form 1.7 to 1.9. I am very new to magento, SSH and mysql. I was just wondering what is the easiest way to upgrade with breaking my website.
Thank you
Upgrade Roadmap for CE 1.9.0.1 from 1.7
take a backup of current database and current 1.7 code.
download latest magento from the http://www.magentocommerce.com/download
remove all folders and files from your 1.7 code (but you should have backup somewhere) and place all folders and files from the 1.9.
now from your 1.7 merge your following folders into the 1.9
Community app/code/community
Local app/code/local
Media
your theme or package (app/design/frontend/default/<your theme> or app/design/frontend/<your package>)
custom folders from Skin (both for adminhtml and frontend).
copy your custom xml files from app/etc/modules/ to current app/etc/modules/
any custom admin theme folder from adminhtml/default/yourtheme.
copy your custom folders from adminhtml/default/default/ (1.7) to adminhtml/default/default/ (1.9).
custom js files if any from app/js/.
now go to app/etc/local.xml.Edit database details there. put your database username and password and database name.
now check the site. it's done.
Current Version Magento CE 1.7.0.2
Admin panel -> System -> Magento Connect -> Magento Connect Manager
Check for Upgrades
Mage_All_Latest -> select Upgrade to 1.9.0.1
You are done!
You should be able to upgrade directly.
As always, third-party extensions and local customizations need to be taken into account, make a proper backup, etc.
The other answer is dangerous and should be taken with care make sure you create a dev server the following article explains
http://www.magentocommerce.com/wiki/groups/227/moving_magento_to_another_server
Upgrade can be done by following these steps(if there are lot of custom modules and you want to ensure your code does not break)
1.Download the latest stable version of your Magento instance.
2.From your older copy, starting copying your custom modules from
app/etc/local.xml
app/etc/modules/
app/community/
app/local/
app/design/frontend/{{package}}/{{theme}}, any custom template files
in default/default/ theme or base/default/ theme needs to be copied.
adminhtml/default/{{custom theme}}
adminhtml/default/default/
skin/frontend/{[package}}/{{theme}}/{{css|js|images}}
same for adminhtml if added any
copy custom files from
js/
3.Make changes to your local.xml and connect it to your older magento database.
Once you run Magento'instance, any core set up updates will be made using the setup files in your core extensions.
PS:- This method runs when you have followed all standards possible i.e no core modifications, correct class rewrites, no changes in index.php,Mage.php etc
Also, if some of the third party extensions if give error, need to update them.
Hope it helps! And if you do try out..let me know how it goes!
Magento 1.x upgrade instruction using SSH or Command line:
1) Go to your Magento root directory
cd /path/to/your/magento/folder
2) Enable Maintenance mode for your Magento site
For this, you have to create an empty file named maintenance.flag in your Magento root directory.
touch maintenance.flag
3) Clear Cache & Sessions
rm -rf var/cache/* var/session/*
4) Check Compilation & Disable it if Enabled
Check Compiler Status
php -f shell/compiler.php -- state
If the Compiler Status is Disabled then you can skip this step and move on to the next step.
If the Compiler Status is Enabled then you have to disable it with the following command:
php -f shell/compiler.php -- disable
5) Give write permission to all Magento files and folders
chmod -R 777 .
6) Give 550 permission mage file which is a shell script file. With 550 permission, we are just making the file non-writable + readable & executable by user and group only.
chmod 550 ./mage
7) Change config settings to stable
./mage config-set preferred_state stable
8) Upgrade Magento
You can list all the installed packages with the following command:
./mage list-installed
You can list all the upgradable packages with the following command:
./mage list-upgrades
The following command will upgrade all the packages:
./mage upgrade-all --force
It will take some time to complete the upgrade.
9) After completing the upgrade, we should reindex all data.
php shell/indexer.php reindexall
10) Then, clear cache and session again.
rm -rf var/cache/* var/session/*
11) Enable Compilation only if it was Enabled before upgrade
Check step 4) above.
If Compilation was not enabled in step 4) then you can skip this step and go to next step.
If Compilation was enabled for your website and you had disabled it at step 4) then you have to Enable it with the following command:
php -f shell/compiler.php -- enable
12) Before the upgrade, we have changed the permission of all files and folders to 777. You should also give proper permission to all files and folders of your Magento site.
Convert files permission to 644 and folders permission to 755
find . -type f -exec chmod 644 {} \; && find . -type d -exec chmod 755 {} \;
Give read-write full permission, i.e. 777 to var and media folders.
chmod -R 777 var media
Give 550 permission to mage shell script file
chmod 550 ./mage
13) Check the versions of the installed modules. The modules should show the latest version as they are already upgraded now.
./mage list-installed
14) List the upgradable modules (modules that need an upgrade). This should result in a message saying No upgrades available because all modules have been already upgraded to the latest version.
./mage list-upgrades
15) Disable Maintenance mode to make the site Live.
rm -f maintenance.flag
This will delete the file maintenance.flag and then the site will be live again.
You can now login to Magento admin and see the Magento version displayed in the footer section. It should show the latest version number.
Source: Magento 1.x – Update / Upgrade to Latest Version via both Browser & Command Line
I am not able to install akeeba backup 3.9.2 version component in joomla 2.5.11 .I have tried it by increasing the upload_max_filesize and post_max_size.And also given directory permissions to the the folders needed. But it still its giving errors "Copy failed -1".Please let me know some solutions to install it.
Some things to try/check:
is there sufficient free space in your web hosting account?
check the permissions on the tmp folder
check the upload_max_filesize in Site -> System Information -> PHP
Information is sufficient for the installation file to be uploaded
try installing a different extension to check if it is issue with the
Akeeba install specifically rather than a permission or file size
issue
try updating to the latest version of Joomla
try installing the latest version of Akeeba Backup (3.10.0 as I write
this)
check the PHP file handler at Site -> System Information ->
System Information -> WebServer to PHP Interface - there could
be a file ownership issue if this is set to the default apache file handler
rather than suPHP or FCGI etc and you may need to escalate this issue to your hosting provider
You should probably update Joomla to the latest version in any case to keep it secure.