I worked all day to get Xampp running and install TYPO3 on it. Now I'm logged in the backend, but many admin modules are not displayed, such as Templates, Access etc. - There must be something I've done wrong, but I've got no idea. these are the modules shown Missing: View, Info, Functions, Template, Access, Backend Users, Log, DB Check, Configuration, Reports.
Most backend modules are shipped as extensions, which can be installed, uninstalled, activated and deactivated.
If you installed TYPO3 by using the traditional installation method (extracting the TYPO3 source package), go to ADMIN TOOLS → Extensions and make sure, the missing modules are activated. For example, "Log" is provided by the system extension belog and "Templates" by tstemplate. You can activate/deactivate extensions by clicking on the icon left-hand-side of their title.
If you installed TYPO3 by using PHP Composer (see documentation), make sure all packages are included in your composer.json file. For example typo3/cms-belog, typo3/cms-tstemplate, etc. You can add/remove packages with the following composer commands on the command line (for example typo3/cms-belog):
composer require typo3/cms-belog
composer remove typo3/cms-belog
In the unlikely event that this does not solve your issue, review file typo3conf/PackageStates.php. This file contains a list of all extensions (system extensions, as well as community extensions), currently available in your TYPO3 system.
It could also be that your admin user, who may have been migrated from an older version, is not a newly introduced system maintainer.
https://docs.typo3.org/c/typo3/cms-core/master/en-us/Changelog/9.0/Feature-82266-BackendUsersSystemMaintainers.html
If that is the case, you can easily create an new "system maintainer user" from the install environment. Maintenance > Create Administrative User
I had the same problem. The required extension were also present in PackageStates.php but still the backend menu options like Admins Tools, Extensions, Maintenance were not visible.
The reason was that that admin user was not listed as a System Maintainer
To make a backend user a System Maintainer do the following
Login with admin password to /typo3/install.php
Setting > Manage System Maintainers
select and save backend users you want as System Maintainers
Now go to backend at /typo3/ and you should see the "Admins Tools" menu options
You can use https://get.typo3.org/misc/composer/helper to figure out the missing extensions. If you simply want to install all extensions, klick on TYPO3/FULL and copy and paste the code to your console.
composer require "typo3/cms-about:^9.5" "typo3/cms-adminpanel:^9.5" "typo3/cms-backend:^9.5" "typo3/cms-belog:^9.5" "typo3/cms-beuser:^9.5" "typo3/cms-core:^9.5" "typo3/cms-extbase:^9.5" "typo3/cms-extensionmanager:^9.5" "typo3/cms-feedit:^9.5" "typo3/cms-felogin:^9.5" "typo3/cms-filelist:^9.5" "typo3/cms-filemetadata:^9.5" "typo3/cms-fluid:^9.5" "typo3/cms-fluid-styled-content:^9.5" "typo3/cms-form:^9.5" "typo3/cms-frontend:^9.5" "typo3/cms-impexp:^9.5" "typo3/cms-indexed-search:^9.5" "typo3/cms-info:^9.5" "typo3/cms-install:^9.5" "typo3/cms-linkvalidator:^9.5" "typo3/cms-lowlevel:^9.5" "typo3/cms-opendocs:^9.5" "typo3/cms-recordlist:^9.5" "typo3/cms-recycler:^9.5" "typo3/cms-redirects:^9.5" "typo3/cms-reports:^9.5" "typo3/cms-rsaauth:^9.5" "typo3/cms-rte-ckeditor:^9.5" "typo3/cms-scheduler:^9.5" "typo3/cms-seo:^9.5" "typo3/cms-setup:^9.5" "typo3/cms-sys-action:^9.5" "typo3/cms-sys-note:^9.5" "typo3/cms-t3editor:^9.5" "typo3/cms-taskcenter:^9.5" "typo3/cms-tstemplate:^9.5" "typo3/cms-viewpage:^9.5" "typo3/cms-workspaces:^9.5"
Related
I recently tried to create an FAQ Page with the TYPO3 extension jpfaq.
I did set up everything as it was described in the manual. But for some reason when i preview the page, it shows a bunch of different error. For example:
TYPO3\CMS\Extbase\Persistence\Generic\Storage\Exception\SqlErrorException
Table 'xxx_typo_dev.tx_jpfaq_domain_model_ttcontent' doesn't exist
When I "unbind" the FAQ database I created it shows me the correct FAQ page (just without the questions and answers). So there might be a problem with the database?
Cleared cache. Deleted and installed the extension again. Didn't help.
Sounds like the you need to fix the Database Structure.
Normally the Database Structure is fixed when you install new extensions in the Extensions module.
If you use Composer Mode the installation is done with composer and you need to fix it by hand.
This can be done in the InstallTool / Maintenance Module: Analyze Database Structure.
Or you use the commandline: vendor/helhum/typo3-console/typo3cms database:updateschema (don't forget to use composer require helhum/typo3-console)
I have a composer typo3 (8.7.30) project, but somehow the extension-manager does not show up.
I tried the following:
./vendor/bin/typo3 extensionmanager:extension:install extensionmanager
./vendor/bin/typo3cms extension:activate extensionmanager
./vendor/bin/typo3cms extension:setup extensionmanager
My user has admin rights and I can see other admin tools. I also tried to create a new admin with the install tool and the new user had the same "problem".
Other modules - including custom ones - are showing up.
Any ideas on how to tackle this?
Edit: When I install the project step by step without generating the package state it's working fine, but the moment I generate package states the extension manager is missing - even though the entry in the PackageStates.php
One userTsConfig.ts disabled the module in the production context. I didn't check for it because the behavior was new for me. It was neither a typo3 or composer problem, just a configuration issue.
After installing from your composer.json, the extension manager is available.
I guess that your PackageStates.php just somehow misses the extensionmanager:
'extensionmanager' => [
'packagePath' => 'typo3/sysext/extensionmanager/',
],
If I manually remove that section, vendor/bin/typo3cms install:generatepackagestates (from the package helhum/typo3-console which you already have installed) would regenerate it.
When I try to open User Manager or just simple do a select * from sec$users, I get an error Missing user management plugin.
I have already seen in some posts how to set usermanager from firebird.conf adding Srp, Srp256, Legacy_UserManager and restart the service, but the error continues.
The only cause I know for this error is specifying a plugin name that doesn't exist.
This can come in two forms:
Specifying a non-existent user manager. For example, Srp256 only exists as an authentication plugin, but not as a user manager plugin. You use Srp as user manager for all SrpXXX authentication plugins. This is technically a specific case of the second form below.
The library containing the user manager plugin is missing from the plugins folder of the Firebird installation. For the Srp user manager, you need to have srp.dll (or srp.so), for Legacy_UserManager, you need to have legacy_usermanager.dll (or legacy_usermanager.so).
Incorrect access rights on files and folders might cause this behaviour as well (though I haven't verified this), for example if the user running the Firebird process doesn't have read access to the plugins folder or to specific plugin files.
Whenever we clone a site on a development machine, the PackageStates.php will be rewritten shortly after and the order of entries will be all over the place, resulting in tons of changes, even though nothing has actually changed logically.
This brings up the question, should the file actually be under version control?
We experimented with ignoring it, but then, when deploying on a new machine, the site will not know which extensions to load. Which suggests to me that it shouldn't be excluded from version control. But then how should the information, which extensions to load, be transferred?
You can include the PackageStates.php to your version control.
You also can exclude it from versioning and generate it automatically during deployment process. typo3-console has a command for this:
typo3cms install:generatepackagestates
In older TYPO3 versions < 9 LTS, you have the option to install extensions based on conditions like context, host, system you can use
$GLOBALS['TYPO3_CONF_VARS']['EXT']['runtimeActivatedPackages'] = array('extension_builder','devlog');
in your AdditionalConfiguration.php.
Article about this topic at typo3blogger.de
If you have a TYPO3 composer installation, PackageStates.php is automatically generated when running "composer install":
https://docs.typo3.org/p/helhum/typo3-console/6.5/en-us/CommandReference/InstallGeneratepackagestates.html
Generates and writes typo3conf/PackageStates.php file. Goal is to not have this file in version control, but generate it on composer install.
Is there a way to load a package from an alternative server when Visual Studio Package Manager (NuGet) is responding with a "The remote server returned an error: (503) Server Unavailable" message?
This is an obscure condition that will likely only occur on an "enterprisy" network environment. If these conditions apply you:
you are required to access the Internet via an HTTP proxy server
the HTTP proxy server requires a valid user ID & password (or AD authentication) to allow requests to proceed
you've been messing with cool developer tools that were ported to Windows from a Linux/Unix environment
the new cool tool(s) work after adding the HTTP_PROXY (or possibly HTTPS_PROXY or both) environment variable(s)
you can access the NuGet servers from a browser without getting a 503 error
Then it's likely you broke NuGet by inadvertently invoking this configuration feature. I'm not sure exactly how the environment variable breaks NuGet but I suspect NuGet is detecting & using the http_proxy URL but sending an empty user ID & password which causes the HTTP proxy to reject the request.
Fix: remove the environment variable(s) you added and see if the cool tool can be configured to use an HTTP proxy without them.
Update: Ran into a version of this issue with the NuGet config file referenced in the "this configuration feature" link above. Open this file:
%appdata%\nuget\nuget.config
in your favorite editor. If it contains elements with http_proxy or https_proxy then removing these elements may fix the issue too.
PS: Hopefully I'll get an up vote from Colonel Panic :-)
If you have used the package in the past it is probably in your cache. You can add the local cache as an available package source by going into the Library Package Manager Settings under the Tools menu in Visual Studio. For Visual Studio 2012, choose Tools, Library Package Manager, Package Manager Settings, and then click on Package Sources.
In the Available package sources section, type a name like "Cache" and then in for the source, browse to %LocalAppData%\NuGet\Cache. You may need to use Windows Explorer to translate %LocalAppData%\NuGet\Cache into the full path (usually C:\Users\YourAccountName\AppData\Local\NuGet\Cache).
Once you have the Cache as an available source, you can now use the Package Manager Console (found under the View menu under Other Windows or also under the Tools menu under Library Package Manager).
From the Console (which is a PowerShell window with commandlets for NuGet) you can type "get-help NuGet" to see available commands.
Then using Get-Package, you can get a list of Package ID's. Make sure the "Package source" is set to "Cache" (or whatever you called it) and the Default project is set to the project you need manipulate, both of these are dropdowns located at the top of the Page Manager Console. You can also use the Get-Project to verify you are working against the correct project in your solution.
Finally, you can type Install-Package and when prompted enter the Package ID from the output of the Get-Package commandlet.
i had also this problem, it was becouse of my network.
if you have any blocking on your Internet, (like in companies internet or etc..)
you may not allowed to download the nuget package.
try to download the package in another network, maybe it can help you!
Talbott's answer did not work for me, as my cache was empty. However, if you have used the package in another solution, you can copy the items you want from the "packages" folder in the other solution to a packages folder in your target solution.
If you have no packages installed in the target solution, you may need to add the following to a repositories.xml file in the packages folder:
<?xml version="1.0" encoding="utf-8"?>
<repositories>
</repositories>
After doing that, the packages appeared to be installed in my solution and I was able to add them to projects.
Additional Note: I had to use the "Manage NuGet Packages for Solution" option at the solution level to add the package to individual projects. Using Install-Package from the console still returns a 503 even though the packages is already installed in the solution.
You can also get this error if you are using a VPN client (e.g. Cisco AnyConnect) and you have recently renewed your VPN certificate. The issue can occur after you have updated your certificate, but before you have rebooted. A reboot resolves the issue.
It is a pretty old question, but I have just encountered the same problem. In my case it occurred because I had more than one nuget package source configured in the Visual Studio Package Manager. In my company we use NuGet to get mainstream packages and MyGet for our own stuff.
When I attempted to pull a pretty big package it failed with a 503 code and the error link looked pretty odd, it had MyGet in it istead of NuGet. Turns out Visual Studio package manager tried to pull it from another source despite having NuGet chosen as a current source. Disabling other sources and then proceeding with a download fixed it.
Hopefully it will help somebody who stumbled upon this thread just like I did.
Another possible reason for recieving 503: If you're using Azure DevOps feed, then NuGet packages are limited to 500 MB.