I have tried to upgrade TYPO3 version 9.0.0 to the LTS version. I have followed the below steps.
TYPO3 version 9.0.0 to TYPO3 LTS
1) Enable symlink typo3_src folder to
ln -s typo3 typo3_src
This showing upgrade button enabled to perform the upgrade.
2) After that, I performed an upgrade process.
Nothing happens when I click the button, this only showing a message like this.
TYPO3 version 9.5.6 to TYPO3 LTS
I have performed the same steps to check the functionality in the TYPO3 version 9.5.6
This download the latest version of the typo3 in the root directory
in the root and shows success message
As per showing in the message, Its tell me to reload browser because the system has been upgraded. But, after reloading it not showing the latest version of the TYPO3.
Can anyone tell me what's wrong with this?
Your symlink isn't set correct.
you wrote:
ln -s typo3 typo3_src
what links in the false direction.
The correct symlinks for TYPO3 (9.5.8) are:
ln -s typo3_src-9.5.8/ typo3_src
ln -s typo3_src/typo3 typo3
ln -s typo3_src/index.php
The ln -s commands syntax is:
ln -s <source> <targetname>
I think your folder structure is incorrect. The correct structure would be:
typo3_src -> /path/to/typo3_src-9.5.x
typo3 -> typo3_src/typo3
index.php -> typo3_src/index.php.
Your command would yield typo3_src -> typo3
First, try ln -s typo3_src-9.5.8 typo3_src and see if that fixes the problem. If it does not, additionally try ln -s typo3_src/typo3 typo3, and then ln -s typo3_src/index.php index.php. It might be, that you have to rename the existing directories/files before this actually works.
TYPO3 version 9.0.0 to TYPO3 LTS: Issue is already found in the core, Please check - https://forge.typo3.org/issues/87575. So, you are facing this problem.
TYPO3 version 9.5.6 to TYPO3 LTS: If your project setup with below symlinks then you need just to follow TYPO3 core update wizard only.
ln -s typo3_src-9.5.6/ typo3_src
ln -s typo3_src/typo3 typo3
ln -s typo3_src/index.php
Please let try it.
Assuming you want to update Typo3 from v9.5.10 to v9.5.25
1 -With the current version (v9.5.10)
cd /var/www/typo3
mv typo3_src typo3_src_9.5.10
ln -s typo3_src-9.5.10 typo3_src
mv typo3 typo3.save
ln -s typo3_src/typo3 .
mv index.php index.php.save
ln -s typo3_src/index.php .
2 - Download the new version (v9.5.25)
wget --content-disposition get.typo3.org/9.5.25
3 - unzip the new version in the /var/www/typo3/ directory
tar xvfp typo3_src-9.5.25.tar.gz
4 - Move the new version of the “core” to its destination directory
cd /var/www/typo3
chown -R apache:apache typo3_src-9.5.25
chmod -R g=u,o=u-w typo3_src-9.5.25
rm typo3_src
ln -s typo3_src-9.5.25 typo3_src
5 - Now the core of your typo3 is version 9.5.25
Related
Clone fresh Magento 2 instance;
2.Run composer:install
Fatal Error:
PHP Fatal error: Uncaught Error: Undefined class constant 'PRE_COMMAND_RUN'
This was an issue with Composer, By installing latest version of Composer solved it.
The bug for the constant variable PRE_COMMAND_RUN is raised and closed.
You need install latest version of composer, upgrade steps given below.
-- Remove existing composer
Debian/Ubuntu
sudo apt-get remove composer
Centos/Redhat
sudo yum remove composer
Get the latest composer using wget.
cd /tmp
sudo curl -sS https://getcomposer.org/installer | php
Move composer executable to PATH so it can be accessible globally.
sudo mv composer.phar /usr/local/bin/composer
To check the composer version
composer -V
You have to reinstall the Composer and use the latest composer version
To do that you can follow the following steps:
Step #1) Remove the current composer:
sudo apt-get remove composer
Step #2) install the composer , you can using following commands
php -r "copy('https://getcomposer.org/installer', 'composer-setup.php');"
php -r "if (hash_file('sha384', 'composer-setup.php') === 'e0012edf3e80b6978849f5eff0d4b4e4c79ff1609dd1e613307e16318854d24ae64f26d17af3ef0bf7cfb710ca74755a') { echo 'Installer verified'; } else { echo 'Installer corrupt'; unlink('composer-setup.php'); } echo PHP_EOL;"
php composer-setup.php
php -r "unlink('composer-setup.php');"
then to make sure you have the latest Composer , run the following command
php composer.phar -V
Now, your ready to install Magento,
to install Magento via composer :
composer create-project --repository-url=https://repo.magento.com/ magento/project-community-edition YourProjectName
if the project folder name is exist , remove the folder and try again to install magento
You probably have an outdated version that doesn't even support self-update unfortunately.
So here's a oneliner to install the latest version in /usr/local/bin:
curl -sS https://getcomposer.org/installer | sudo php -- --install-dir=/usr/local/bin --filename=composer
Check:
which -a composer
/usr/local/bin/composer --version
composer --version
Composer self-update wasnt working with my composer version, I use ubuntu(LEMP).
Latest version of composer was installed - 1.6.3 I think.
We need this 1.10.17.
sudo apt remove compsoer
php -r "copy('https://getcomposer.org/installer', 'composer-setup.php');"
php -r "if (hash_file('sha384', 'composer-setup.php') === '756890a4488ce9024fc62c56153228907f1545c228516cbf63f885e036d37e9a59d27d63f46af1d4d07ee0f76181c7d3') { echo 'Installer verified'; } else { echo 'Installer corrupt'; unlink('composer-setup.php'); } echo PHP_EOL;"
sudo php composer-setup.php --version=1.10.17 --install-dir=/usr/bin --filename=composer
Check version:
composer --version
output: 1.10.17
To be sure remove all vendor and cache:
rm -rf vendor/*
composer clear-cache
composer update
At present time Devtoolset-5 (and earlier) cannot be istalled from Software Collection Repository (centos-release-scl) using yum (only Devtoolset-6 and 7 are available). Nevertheless, this collection can be downloaded as a list of rpm-packages. Is it possible to enable such EOL collections for yum, or maybe there is another way to install them correctly?
There was no DTS 5 release. It was skipped to align the DTS version with the GCC major release, once GCC switched to a yearly increasing version number.
DTS versions 3 and 4 are available from the centos-release-scl repository.
While Devtoolset-3 and 4 are located on the Centos mirror site, yum will not be able to find them as they were not included in the repodata on the site. These were probably excluded because they are EOL (end-of-life), and have dependency bugs (Bug 1410152). Try using the older Devtoolset-3 packages here, which do not have the dependency issues:
https://copr.fedorainfracloud.org/coprs/rhscl/devtoolset-3/
If you really want the packages from the centos.org site, I went with wget to download all the RPMs, then recreated a local yum repo. However, you'll see the dependency issues and yum install devtoolset-3 will fail.
$ wget -r -p -e robots=off --directory-prefix="/mnt/local-devtoolset3-repo" --recursive --no-clobber --no-parent http://mirror.centos.org/centos/6/sclo/x86_64/rh/devtoolset-3/
$ sudo yum install createrepo
$ cd /mnt/local-devtoolset3-repo
$ createrepo --database .
You can install the obsolete devtoolset-3 in this way:
sudo yum --obsolete install devtoolset-3
I'm working on an theme based on blank theme (Magento 2.2.5) on developer mode as well as production mode the theme less files are not compiling using:
rm -R pub/static/*
php bin/magento setup:upgrade
php bin/magento setup:static-content:deploy
Images are loaded ok, not css. No errors using verbose. The only way is using grunt both for development and production for my theme what can i do?
Solving this issue is actually simple; just run the following command
Clear the var/cache and var/view_preprocessed directories by deleting the directory in
sudo rm -R pub/static/*
sudo rm -R var/cache
if you have to (sudo rm -R generated/code)
sudo rm -R var/view_preprocessed
sudo php bin/magento setup:upgrade
sudo php bin/magento setup:static-content:deploy -f
If you are in production mode, delete var/view_preprocessed and var/cache, run the CLI for setup upgrade and then static-content deploy. That should work.
octave:1> doc fflush
info: /usr/local/Cellar/octave/3.6.3/share/info/octave.info: No such file or directory
I'm not sure what I've done wrong with my installation, but I get the msg above when attempting to find the documentation (help fflush works fine). Does anyone know how to fix this issue?
I had the same problem and solved it with manually decompressing the corresponding deb archive to the respective place of the brew installation:
Download the deb from here : http://packages.ubuntu.com/de/quantal/all/octave-info/download
cd ~/Downloads
mkdir doc
cd doc
ar -x ../octave-info_3.6.2-5_all.deb
tar xzf data.tar.gz
cd usr
find . -name '*.gz' -type f -exec gunzip "{}" \;
cd ..
cp -r share /usr/local/Cellar/octave/3.6.4/
cd ~/Downloads
rm -r doc
You have to adjust the octave version numbers to match the most recent and your brew cellar of course.
I don't know about Mac OSC. If you had built it yourself, could have been that you disabled the documentation at build time. With a package manager... you already checked that it does not have a separate octave-doc package.
There's a bunch of other package managers for Mac that have Octave. See Octave's wiki. Taking a quick look at the other package managers, it seems that they all have separate packages for docs.
If I add non-ASCII characters to MongoDB database then all db.find() fail telling "non ascii character detected".
It's problem of SpiderMonkey, I have to rebuild it with UTF-8 support.
I've tried to do it like in
http://www.mongodb.org/display/DOCS/Building+Spider+Monkey
but it doesn't work (SpiderMonkey is not installed after I've completed all steps).
I've got Ubuntu 11.04. Does anybody have instruction how to make it work there?
Working instruction how to make work MongoDB with Google V8 can also help.
I'm using MongoDB on Ubuntu Server 11.04, installed it after making fresh OS install using this instruction: http://www.mongodb.org/display/DOCS/Ubuntu+and+Debian+packages
Everything is working fine out of the box. Is it critical for you to build MongoDB from scratch?
Using the 10gen-published packages works fine, but if you actually want to compile SpiderMonkey from source with UFT-8 support:
curl -O ftp://ftp.mozilla.org/pub/mozilla.org/js/js185-1.0.0.tar.gz
tar xvzf js185-1.0.0.tar.gz
cd js-1.8.5/js/src
export CFLAGS="-DJS_C_STRINGS_ARE_UTF8"
export CXXFLAGS="-DJS_C_STRINGS_ARE_UTF8"
And then follow the instructions from https://developer.mozilla.org/En/SpiderMonkey/Build_Documentation
autoconf-2.13
./configure
make
make install
cp js /usr/local/bin/
This will install into /usr/local/lib, however the mongodb package looks for it in /usr/lib (where the spidermonkey package is installed). So, we link all files installed to /usr/local /lib from /usr/lib
ln -s /usr/local/lib/libmozjs185.so /usr/lib/libmozjs185.so
ln -s /usr/local/lib/libmozjs185.so.1.0 /usr/lib/libmozjs185.so.1.0
ln -s /usr/local/lib/libmozjs185.so.1.0.0 /usr/lib/libmozjs185.so.1.0.0
ln -s /usr/local/lib/libmozjs185-1.0.a /usr/lib/libmozjs185-1.0.a
Of course you could just move them into /usr/lib instead of symlinking, but I wanted to keep the utf-enabled libs away from the default location, to prevent conflicts with the default spidermonkey package. Without the libmozjs package installed, apt complains that dependencies for mongodb are not satisfied, so I've left it installed.
Keep in mind that if the spidermonkey package gets upgraded, it can overwrite the symlinks to our new libs (or the libs themselves if you've moved them to /usr/local/lib). The ideal solution would be to build your own package to solve dependency issues for good.