I fumbled around with an ancient T3 installation (tried an upgrade from 4.5 to 6.2) and before the fumbling created a backup from the entire directory on the webserver as well as the database.
Now I tried to re-activate that backup (a.k.a. 4.5). The install tool works fine, DB-Connection seems to be ok, but when I try to access the backend, it tries to access /typo3/sysext/install/Start/Install.php which isn't present at the described location.
I tried to delete all caches, emptied the typo3temp folder - nothing helps. It seems there's something stuck from the upgrade process, but I have no idea where.
Any ideas?
The Problem's solved. T3 6.2 uses the PHP Opcode Cache which can't be reset in the 4.5 install tool. Something must have been stuck there. I wrote a little PHP script that clears the cache and viola, it worked.
opcache_reset();
Related
I am trying to upgrade the site from v 7.6 to v. 7.15.1.
I have done the upgrade on localhost which included updating the db.
Now I transferred my files from localhost o the test site and on there I am getting an error in log:
ERROR Umbraco.Core.UmbracoApplicationBase - An unhandled exception occurred
System.Data.SqlClient.SqlException (0x80131904): Invalid object name 'umbracoUserLogin'.
and I can't login to the backoffice.
It seems to be looking for umbracoUserLogin on test while it doesn't exist yet because on test the db is not updated yet.
How to update the db on test in this case while the files have already been updated on localhost and transferred to test site?
I have done 2 umbraco upgrades recently; one is from 7.5.7 to 7.13.1 and the recent one is from 7.13.1 to 7.15.1.
During my upgrade; I have seen this problem and fix in this issue can help you for your problem(and I didn't see this problem again after doing the upgrade again, but this time checking all the auto changing files and accepting them one at a time-see details below for this) but coming back to your question; "What's the best way to upgrade from umbraco 7.6 to 7.15.1(including db upgrade)"; here are the steps that you should follow;
Create a backup for your project and your umbraco db before you start. If you are using Git, then things will be super easy for this.
Open up Nuget Package Manager for your Umbraco project and do the package upgrade using the Nuget Package Manger window or the consol. Search for UmbracoCms version 7.15.1 for your case.
Once you start doing the upgrade, you will see some popup windows that will ask you to approve some auto file changes(including some config files changes). As you don't want to lose some of your pre-upgrade settings, don't accept them all or discard them all, check all of them one by one, and as a general rule; if you don't have any custom changes for those files, then simply approve the change, otherwise, check your changes and make sure you don't loose anything and discard some of these file changes as a result.
Once you're done with your UmbracoCms upgrade(which will automatically do some dependency package upgrades), build your project, make sure all is looking good then go to your local project's umbraco back-office url, this will trigger the rest of the umbraco upgrade process and simply complete the upgrade steps by following the screens- at this point your umbraco db changes will be done automatically and it is possible that you might have some issues with some old corrupt cached files, if this happens, then simply delete App_Data/TEMP files and App_Data umbraco.config file and try again. If you see some other problems during the installation, check the logs(browser developer tools can be handy to understand the problems in this case), and fix them one at a time. It is possible that you don'T need some of your old web.config settings and they might cause some issues, simply comment out those lines and see if this will fix some of the issues.
Once you are done with you local upgrade, deploy your code to your testing environment, and go to the umbraco url of your test environment and follow the screens to complete the installation for your testing environment. If you see any problems, please check my notes for step 4 above.
Do your umbraco upgrade for other testing environments(QA, UAT, Training etc) and complete your umbraco upgrade tests. Once the tests are done, then you are ready to go live. After the live deployment, you will have to complete the umbraco upgrade one last time, but this time for the live system.
Always get your back-ups for each environment before you do the upgrade, so you will be ready to rollback your changes if things go wrong(which might happen as you're doing a big umbraco upgrade).
Final note; there are some good articles for this, please take a look to understand the process better. Good luck!
Since upgrading from MAMP 3 to MAMP 4, the GUI hangs on each action. Clicking something like the menu occurs after around 30 seconds of the spinning wheel of death. This happens for any action within the interface. Running 10.12.2
This almost makes the software unusable, as I can't configure the interface to begin development.
My experience was identical. Searching for some errors I ended up running Tools > Verify MySQL Databases... Among tons of OK'ed databases, several had errors - innodb_index_stats, innodb_table_stats, slave_master_info, slave_relay_log_info, and slave_worker_info.
From here a search lead me to mysql error: Table “mysql”.“innodb_table_stats” not found.
So, I deleted all the .frm and .ibd of the tables above and I ran the five-tables.sql file in Terminal: source five-tables.sql
Now MAMP Pro 4 runs smoothly and responsive.
Thanks, Kay Nelson.
I ended up doing a search for MAMP in all parts of the file, and removed every reference to it, after running the uninstaller.
I also removed references to any PHP & memcache not in the /Applications/MAMP folder.
I renamed /Applications/MAMP to /Applications/MAMP-old and reinstalled. This set everything up fresh and appears to be working. Something with a conflict with a system binary or other package was causing the issue.
Help is requested to delete a database I have created in TYPO3 setup.
I have installed XAMPP in Ubuntu 16.04 and configured it correctly and it runs. Now I was in the process of configuring TYPO3 in XAMPP using this very good guide.
After creating the "typo3cms" database, the next stage asked for a user name and password. I think I was supposed to put in my Ubuntu username and password, but erroneously I put in a new username and password and got the error of not being able to connect to my database.
I tried to go back to the previous stage of creating a database, which I can't because it already exists. But then I cannot go forward anymore. I have no idea where the database resides so that I can delete it and recreate it. I have tried uninstalling typo3 and reinstalling it. I have tried to google the problem without success.
Short of purging xampp completely and starting from scratch, is there a way I can delete the typo3cms database I have created?
It sounds like you are so early in the install process that you can start over (by removing all files and doing the install from the beginning).
Alternatively you should be able to remove typo3conf/LocalConfiguration.php and make sure that FIRST_INSTALL exists in document root (this is an empty file used to indicate that TYPO3 is doing the first install, it gets removed after - and you can use touch FIRST_INSTALL in terminal to create the file). Or if you prefer a completely manual approach, manually edit the typo3conf/LocalConfiguration.php file to correct or remove the database credentials and then resume the install.
At present I cannot run it (SQL Developer 4.1) because it hangs on "Restoring Editors" while starting. I suppose I've done it by exiting it before by killing sql developer process because it was hanged on fetching objects to Schema Browser so long...
Maybe I would clean some temporary files but can't find any.
Any ideas?
Deleting files from c:\Users\MY_USER\AppData\Roaming\SQL Developer\SQL History
and c:\Users\MY_USER\AppData\Roaming\SQL Developer\System...
Really helped me to resolve the connection issues
Basing on this thread https://community.oracle.com/thread/2564842 I've created own solution.
Extract installation of current version SQL Developer (4.1.0.17.29)
At "c:\Users\MY_USER\AppData\Roaming\SQL Developer\"
I've changed directory name system4.1.0.17.29 to system4.1.0.17.28.
After running newly extracted SQL Developer (4.1.0.17.29) I was prompted to let copy configuration from version 4.1.0.17.28 to 4.1.0.17.29 ;)
Everything works great now. I suppose that running the same (broken) installation after decreasing version could also help.
Remove folders c:\Users\USERNAME\AppData\Roaming\SQL Developer\system4.1.3.20.78\system_cache*. SQLDeveloper will recreate it after launching.
Just execute sqldeveloper as administrator. It works fine!
In my case the problem was because of windows compatibility issue. So I've selected my windows version and it's stop from randomly crash after startup
Our setup:
Windows 10
Sqldeveloper Versions <= 20.4.0
We observed this problem as well. Even worse while working over a VPN connection. I followed a couple of hints with more or less no effect.
To move
C:\Users\<USER>\AppData\Roaming\SQL Developer
to a local directory by adding this line
AddVMOption -Dide.user.dir=c:\temp\sqldev-conf
in the \sqldeveloper\bin\sqldeveloper.conf file gave us some improvement, but the “IndexPreferencesTask” still got stuck several times on startup.
After some more hours on unsuccessful research, we moved back from JDK 11 to JDK 8.
This solved 99% of the problem. The “IndexPreferencesTask” still hangs on startup but for less than a second.
Sounds to me like a problem with JDK 11.
In my case when i changed Tools --> Preferences --> Environment -> Look and Feel to Windows it is solved.
Delete the History files from C:\Users\User\AppData\Roaming\sqldeveloper
Restart the PC
In my case, the solution was kind of weird. After battling to resolve this for 2 days, no luck. Suddenly, on my mac, I searched for sql developer, not sqldeveloper. It popped up a sqldeveloper application (not sure how that is different from what I have been trying to open ), clicked it and boom, it opened. My guess is that there is a copy of that app on my system that I should have been opening rather than trying to open the reinstalled app. Note: I reinstalled the app after it started misbehaving though.
Operating System: Windows 10
Oracle Sqldeveloper Ver: 17.4.0
The problem has been noticed sometime when any network security
patch was installed on your machine. Looks like the patch impacts
your cached data under your user profile folder.
As above Lakh, rtbf and others answered. Removing below folders
will resolve the issue.
C:\Users\<userId>\AppData\Roaming\SQL Developer\SqlHistory
C:\Users\<userId>\AppData\Roaming\SQL Developer\system17.4.0.355.2349
If any one find more approriate reason please feel free to
disagree with my answer.
I haven't been able to find any resources on how to do this.. Anyone have any ideas or resources?!
I've tried changing the ./configure options and I'm solving things one at a time but it seems like this method could take forever.. My current error is..
checking for jpeg_read_header in -ljpeg... no
configure: error: Problem with libjpeg.(a|so). Please check config.log for more information.
I'm running Snow Leopard.
Any help would be great,
Matt Mueller
I know this is an old question- but still relevant.
I'm updating my MAMP and am keeping up to date on PHP's stable releases by using a guide I found at davidgolding.net
The Guide goes as follows:
First, run the
phpinfo()
function in a PHP script on your localhost or go to PHPMyAdmin and hunt down the configuration page. You should see a large chunk of configuration markup at or near the top:
'./configure' '--with-mysql=/Applications/MAMP/Library'
'--with-apxs2=/Applications/MAMP/Library/bin/apxs'
'--with-gd' '--with-jpeg-dir=/Applications/MAMP/Library'
'--with-png-dir=/Applications/MAMP/Library' '--with-zlib'
'--with-freetype-dir=/Applications/MAMP/Library'
'--prefix=/Applications/MAMP/bin/php5' '--exec-prefix=/Applications/MAMP/bin/php5'
'--sysconfdir=/Applications/MAMP/conf/php5' '--with-soap'
'--with-config-file-path=/Applications/MAMP/conf/php5'
'--enable-track-vars' '--enable-bcmath' '--enable-ftp' '--enable-gd-native-ttf'
'--with-bz2=/usr' '--with-ldap' '--with-mysqli=/Applications/MAMP/Library/bin/mysql_config'
'--with-sqlite' '--with-ttf' '--with-t1lib=/Applications/MAMP/Library'
'--enable-mbstring=all' '--with-curl=/Applications/MAMP/Library' '--enable-dbx'
'--enable-sockets' '--enable-bcmath' '--with-imap=shared,/Applications/MAMP/Library/lib/imap-2006i'
'--enable-soap' '--with-kerberos' '--enable-calendar'
'--with-pgsql=shared,/Applications/MAMP/Library/pg' '--enable-dbase'
'--enable-exif' '--with-libxml-dir=/Applications/MAMP/Library'
'--with-gettext=shared,/Applications/MAMP/Library' '--with-xsl=/Applications/MAMP/Library'
'--with-pdo-mysql=shared,/Applications/MAMP/Library' '--with-pdo-pgsql=shared,/Applications/MAMP/Library/pg'
'--with-mcrypt=shared,/Applications/MAMP/Library' '--with-openssl'
Copy and paste this whole chunk into your text editor and remove the single quotes (search and replace should do it). Look for the flag
--with-pdo-mysql=shared,/Applications/MAMP/Library
and replace it with:
--with-pdo-mysql=/Applications/MAMP/Library
If you don’t do this, you might end up with an error.
ld: symbol(s) not found
Finally, add the following flag to the end:
--without-iconv
After you have downloaded the latest PHP release of your choosing from PHP Sources Snapshots,
cd
to the downloaded directory in Terminal. Paste your reformatted configuration string (all of it, including the beginning ./configure command) and run it.
After the configuration phase is finished, run:
$ make
$ sudo make install
Relaunch MAMP, and you’re good to go.
The current version (1.9) of MAMP / MAMP PRO includes PHP 5.3 and is available on the MAMP download page.
This is bound to cause a lot of headaches. The simplest solution is to navigate over to the mamp website and grab the latest version of the application. Download it, hit the install button and you will find your php version has been updated to the latest version...
Hope this helps, I spent quite a bit of time fiddling about with upgrading PHP before I actually looked :S
I don't know if MAMP has changed its configuration in the last few years but none of the solutions here helped me. What I did, and what worked right away was:
Download the PHP version you want from MAMP
Unzip it and move the new PHP folder into the MAMP/bin/php folder where you will see other subfolders with names like php5.3.7
Restart MAMP
Go to the PHP panel under Server in MAMP and choose the new verion of PHP from the drop menu
Start MAMP.
reinstall whole MAMP is very safe. You dont even need to take a copy of old MAMP. the new install does it on its own. just feel free to download new MAMP and click install. only care u need to take is this
Edit httpd.conf and open up line to include vhosts.conf and copy old vhosts.conf from old MAMP folder.
Goto MAMP Download page
then choose
an update from the Heading
"Additional PHP versions for MAMP PRO 2.2"