I tried manually upgrade TYPO3 from 7.6.6 to 8.7.16 and received: Oops, an error occurred! I can't login to TYPO3.
I apologize for the brief description but I was very tired after a many hours trying to remove the errorenter image description here. The error looks just like the image, but at the beginning there was a white screen ...
Over the years I have not had problems installing TYPO3 (still Versions 3 and 4), but I had a break in use. I do not have access to SSH. I also assume Symlink was mistakenly set by the admin, and that's why I had to do it manually.
https://docs.typo3.org/typo3cms/InstallationGuide/QuickInstall/GetAndUnpack/Index.html
Similarly, because I did not have access and I did it manually... I noticed that there are also changes in installation, perhaps a problem.
First step to do after an upgrade is to open the install-tool primary to alter tables for new requirements:
example.com/typo3/install.php
There you have to open the upgrade-wizard and follow the shown steps.
You also get the option shown to install compatibility-7, an extension that adds a compatibility-layer for older extensions. You can enter that step and afterwards still decide if to install it or not. In the wizard the logic is that the option will be shown and no matter about your decision it will be marked as done, so that it won't be shown another time again usually.
In your case it's better to follow the update-instructions rather than the install-instructions: https://docs.typo3.org/typo3cms/InstallationGuide/Upgrade/Index.html
Related
Hi everyone I am experiencing a problem with my Backpack license, I bought the license for a single project, and I have inserted the license into my .Env file as described in the documentation:
BACKPACK_LICENSE=XXXX-YYY-ZZZZ-XXXX-YYY-ZZZZ.
And set APP_ENV=production.
The system seems to recognise the licence correctly (no yellow warning is shown when logging in), however when I try to edit my users, the yellow warning appears with the words: "User editing is disabled in the demo version".
What's wrong?
I should point out that I have not activated the cache, but as a test I have also run the command as suggested: php artisan config:clear, but I still get this warning.
Can anyone help me? Thank you.
It sounds like you've created your project starting from the Backpack demo. That's just an example Laravel + Backpack installation, to show off its features, it should not be used for real-life projects. Notice the demo docs page says:
Don't use this demo to start your real projects. Please use the recommended installation procedure. You don't want all the bogus entities we've created. You don't want all the packages we've used. And you definitely don't want the default admin user. Start from scratch.
I recommend you create a new Laravel project, then install Backpack on top of it, then copy-paste your custom code in that new project. That will not only fix the inability to edit things, but many other problems like the ones listed in the quote above.
We upgraded a TYPO3 installation from 8.7.x to 9.5.19.
Afterwards, the User-Icon dopdown in the top toolbar is missing. (see screenshots)
We found out that the toolbar is generated in this class:
/typo3/sysext/backend/Classes/Backend/ToolbarItems/UserToolbarItem.php
We see that there have been lots of changes here since v7.6 but don't know where to go from there.
Is there a configuration file, where the items in the top bar are noted?
Additional information: we are working with the typo3-themes extension and have worked with our own theme before the update. During the update we switched to the bootstrap4 + bootstrap4-child theme - would this be a starting place for further investigations?
Before upgrade:
After upgrade:
UPDATE: It seems like this was at least not the root of the problems. After reactivating typo3_console the user-icon was still visible. So it looks like we have further investigating to do.
Update (2 Days later):
We can't reproduce the error. My best guess for now is, that deactivating the extension "repaired" a corrupt configuration file which had caused the disappearing of the user settings icon. After a lot of researching i have not found anybody with a similar problem so this might be an edge case. I wish i could offer more insight to this.
Thanks to Peter Kraume's basic suggestions i found the answer: after i deactivated the extension typo3_console it immediately worked!
Just for the record, here are the other steps we tried:
BE (via top bar)
Flush frontend caches
Flush all caches
BE Admin Tools ("Maintenance")
Flush TYPO3 and PHP Cache
Remove Temporary Assets
Logs
BE System log shows no current errors
Shared Hosting, /var/ contains no logs, /logs/ contains ftp and access logs
Hosting Provider Backend
Cleared OPcache
Created a new Admin-User, logged in, same behaviour
Tried on two different PCs
Primarily tested on Firefox 77.01, checked with Chrome 83.0.4103.116
Extensions:
was not sure, which extensions might manipulate the topbar - deactivated typo3-console, because i remembered seeing some error during the upgrade process. My feeling was more like: i don't need this right now, so i could as well deactivate it. 1 second later, the user drop-down reappeared. Unbelievable! Thanks for reminding me of the basic stuff - like turning off things!
We just had the same problem after upgrade from TYPO3 8 to 9. I have compared the working BE-User with the non-working BE user. They differ in given Language. Working BE-User has lang=''. Non-Working BE-User lang='de'. After switching the working BE-User to lang de, too, the UserToolbar is gone. I have updated the languages in Maintenance-Module and now everything works as expected.
Solution for us was to disabling the "belog" extension.
I had the same problem and I could solve it on all systems with:
Install-Tool > Maintenance > Manage Language Packs > Download the files again.
I am trying to install TYPO3 v9.5.3 for the first time and fail in the last step of the installation routine (after submitting the form with the login details for the admin user).
As far as I could track this issue down, I think the problem is that I don't have the required library for argon2i compiled into PHP.
Now I found a very similar problem description here, but I am not able to change the algorithm in the process of the installation.
Is there a way to use "bcrypt" or "phpass" right from the beginning (during installation)?
According to https://docs.typo3.org/typo3cms/CoreApiReference/ApiOverview/PasswordHashing/Index.html, PHP 7.2 brings Argon2i support out of the box.
Also, this documentation page also says it falls back to other hashing algorithms if argon2i is not available.
So I guess that your guess about the missing lib is not the real reason.
Your question also does not explain what your actual error/problem is, so there is nothing more we can do here.
Untested but you can try to create typo3conf/AdditionalConfiguration.php before starting the installation process and put this into the file:
$GLOBALS['TYPO3_CONF_VARS']['BE']['passwordHashing']['className'] = 'TYPO3\\CMS\\Core\\Crypto\\PasswordHashing\\BcryptPasswordHash';
Im running a few issues in my Joomla site. All of them are related with Joomla articles.
After saving articles the changes don't apply and the page doesn't stop loading...
If I create a new article and save it seems to be fine but If I get into the article the title and content don't come up. Its absolutly empty.
After trash an article I get the following warning: "null primary key not allowed"
I've tried the following to frigure it out:
Reinstall Joomla core Files
Turned on Joomla Debug to see errors and Turned off some plugins
Fix Database
Any idea about it?
The site is running the latest Joomla 3.6.2
I accidentally published Composite C1 from Visual Studio with "Precompile during publishing" when I first set it up and have now come to realize that several plugins do not work with precompile turned on. Unfortunately I have no idea how to reverse this. I've tried several things to no avail. I usually end up with a 500.0 error. If I go to the admin interface everything is working properly, and I can even preview the pages, but from the customer side all I get is a 500.0 error.
Of course I could republish from the Visual Studio project I have, but that project has the default template on it. I've tried copying what appears to be changed on the server to the original project but I end up with a 500 error. I've tried removing all the precompiled stuff on the server but I end up with a 500 error. I'm pretty lost.
At this point I'm willing to do anything. Is there a doc explaining how to copy the content to a newly downloaded copy, kind of like an upgrade doc but "side-grading"? I am using the most current version at the time of writing this 4.2 Update 1
Thank you
Solved use the PackageCreator suggested by wysocki's answer. It was not exactly straight forward to create the package. The errors can very cryptic at times. So here are some of the issues I encountered and how I got past them:
wysocki was correct to suggesting starting with a bare bones installation even though my original project was started with the Venus theme. I tried both ways.
I encountered issues with the MasterLayout and the Page Template Features which are currently not supported by the PackageCreator, although they may be supported in future versions. The solution was to add the missing elements to the fresh C1 project from the original C1 installation in the App_Data/PageTemplates and App_Data/PageTemplateFeatures folders.
A few times I ran into an issue where I added the same page or function twice to the PackageCreator. This was obviously my fault, but it should be mentioned that you can add the same site element twice which throws and error on import. Make sure you are careful to only getting one of each when creating the package to be exported.
If you are getting and error and it uses and Id like "4061397b-ee9e-4512-984d-f2b2d41eb654" I've found that it was very helpful to extract the zip file you are trying to import and then search the extracted folders for that Id. The lines with the Id usually have more information on them that will help you to identify exactly what content page or whatever the error is being generated from.
If you are using installed packages in your project like SimpleSearch for example, make sure you don't add it's functions to the PackageCreator. Install them separately.
I had an issue where I somehow had an element in the Data section that didn't have a "type". The error simply "The type cannot be empty". This was obviously tough to find so I suppose the lesson is, less is more. If you think your project might have a few elements that are unnecessary, don't add them at first and see if the project you import them into complains about missing them. It's much easier to troubleshoot missing elements than it is to figure out which element is causing the issue that you really didn't need.
Is there a doc explaining how to copy the content to a newly downloaded copy
You can try and export content / templates / anything else related to a "package" via Composite.Tools.PackageCreator.
Its latest version gives you quite a lot of flexibility in what you can export ("package") - please its user manual.
Once the package is made and downloaded, you can go on and install it on a new website. If you export / import a lot of content / templates etc, it makes sense to have a "Bare Bones" site as the new one.
All the starter sites like "Neptune", "Venus" are installed as a bunch of packages in specific order during Composite C1's initial setup.