I have few sites still running on CI 2.2.2. and wanna updates those to 2.2.3 but I don't know what are the modification files. So what files do I need to change in-order to upgrade form CI 2.2.2 to 2.2.3.
As stated here http://www.codeigniter.com/userguide2/installation/upgrade_223.html you need only to replace the system folder and index.php file with the new one:
Replace all files and directories in your "system" folder and replace your index.php file. If any modifications were made to your index.php they will need to be made fresh in this new one.
Related
I started using ddev about 3 years ago to develop my websites on typo3.
I followed this tutorial to be able to develop my exts locally:
https://t3planet.com/typo3-tutorials/install-local-typo3-extensions-composer-mode/
I noticed that since version 11 (and especially with version 12), symlinks can no longer be used to develop local extensions.
Is there an alternative way to be able to recreate the same functionality in typo3 v12 (composer 4)?
I read something on the subject in this link: but I don't understand how to configure it ...
https://docs.typo3.org/m/typo3/tutorial-getting-started/main/en-us/Extensions/Management.html
This is the correct tutorial, yes: https://docs.typo3.org/m/typo3/tutorial-getting-started/main/en-us/Extensions/Management.html#installing-local-extensions
Create a folder in project root, e.g. packages
Create your extension inside a sub folder in packages
Add a composer.json in your extension
Add the repositories part in your root composer.json (not extension)
Require the extension with composer req vendor/extension-name:#dev
Bad mistake this morning. I uninstalled WAMP Server which deleted the Wamp folder and all its projects.
I restored the wamp folder from backup. WAMP is up and running on upgraded PHP and settings as before, however:
Laravel projects won't start - getting blank whoops pages on any Laravel project. When I cd into any project folder and try to run php artisan, I get:
Unable to load the "app" configuration file.
The 'config/app.php' does indeed exist. And, all the restored files appear correct.
As a test, I installed a new Laravel project and it works correctly. I also am able to clone a project from a Git repo, npm update & composer install, and that works. So, I don't think the problem is with the WAMP stack.
I need some direction troubleshooting this. Thanks!
The problem is that Windows changes the case of some file names during restore. What a drag. There seems to be no reasonable answer except make the switch to Apple.
For example, in the Laravel config folder, Windows restored these files with proper case, App.php, Auth.php, Queue.php, and View.php. Everything else was left lowercase as they need to be.
Correcting the case of these files fixed the problem for now (until I find other mis-cased files).
Make sure this file exist
config/app.php
When I change ruby-version files e.g. rvm --ruby-version use a.b.c#rails_4
I get a message along the lines
.ruby-version is not empty, moving aside to preserve.
.ruby-gemset is not empty, moving aside to preserve.
and two new files are created that store the old version of the ruby version and gems name. This clutters up my root directory, is there an flag to stop this happening? If not, any reasons why I should not just delete the old version files?
rvm --ruby-version use a.b.c#rails_4 command is used to create .ruby-version file that represents your project's Ruby version. This file is intended to be stored in your repository, but I guess you already know that.
Anyways, as the docs say, it is used for creating and not updating or anything. So, it is logical that RVM first backs up existing .ruby-version and .ruby-gemset files before generating the new ones.
You can delete those backed up files. If you want to update the ruby version of your project just edit existing .ruby-* files. It is much easier IMHO.
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 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.