When I try to load the RolesCrudController using Backpack for Laravel it doesn't load any of the roles and just shows an error saying Error Loading Page, please refresh the page.
When I look at the console there is a 500 internal error referencing role/search.
If I type something into the search box it will return matching roles correctly and I can edit the roles. It's just when I initially load {{ backpack_url('role') }} and have nothing stored in the local storage for the search field on this controller that I get the error above.
I'm using the latest version of backpack and the latest version of the permissions manager.
I've cleared the cache, routes, views, configs. This doesn't help.
Related
I have the following problem:
After trying to change the entry point to my website in the backend of my TYPO3 system (by using the site config), I cannot access neither my backend nor my frontend of the website anymore. Whenever I try to access the site it says "Oops, an error occurred! The parsedUri "https://" appears to be malformed".
What I have tried, is accessing the config.yaml on my webserver to change the baseURL inside of the config, but no matter what I change it to, it doesn't seem to work, as I always get the same error message even uploading the changed config file (what I mean by that is, that the text inside the error message doesn't change to reflect the new url but stays "https://").
I hope that someone who is more experienced in TYPO3 can help me solve this issue. I couldn't really find a working solution after extensively searching so far. Thanks a lot in advance.
After changing the yaml file of the site configuration, you need to clear all caches, either via the install tool (yourdomain.tld/typo3/install.php) or by deleting all files in the directories var/cache/code and var/cache/data.
I was fixing things on a not well-maintained typo3 installation and it resulted in blank pages of frontend, backend and install tool.
I wanted to fix extensions because the powermail-extension was not working anymore even after updating to latest compatible version (tried emptying cache and database compare).
I deactivated an extension "compatibility6" to see if it was interfering and since then all pages have been blank including Install Manager. I reactivated the extension via PackageStates.php, emptied the cache but it did not change anything. I was not able to see any error messages even though I set the parameter in LocalConfiguration.php which made it hard to try to find out what is wrong. Then I restored a backup using vmware. Still, backend and frontend are blank.
I am using Apache and Typo3 7.6.23.
I do not know what might be causing the problem and would like to know what else to look for?
It means you have a PHP error there. The first thing would be to examine logs. If you see anything like "class not found", then your next action would be composer dumpautoload --no-dev.
Long time ago I had an article about blank pages in TYPO3 FE. Not up to date but still can be helpful: https://www.dmitry-dulepov.com/2009/03/blank-empty-page-in-typo3.html
Dmitry already wrote it: you have an error.
In production environment nothing is shown for not revealing any information about your system.
So the only information about the error can be found in the error log of your webserver.
What can you do to get more information about your error?
Enter the install tool and switch to develop mode. This will also enable deprecation logging into a file. Try to avoid filling your system with deprecation warnings by disabling deprecation logging.
Disable the default exceptionhandler by adding this to your typoscript setup:
config.contentObjectExceptionHandler = 0
Now you should see a call stack instead of blank screens.
Be aware that this might reveal confidential information from your system.
because of this you should use a copy of the live-system.
I'm currently running TYPO3 version 8.7.18 and running a site_package that was made by using the site package builder: link
Whenever I try to add a form by using the default backend forms module I get the default message Oops, an error occurred! along with that the following error
TYPO3\CMS\Form\Domain\Configuration\FormDefinition\Converters\AddHmacDataConverter not found
Searching for the issue I get several hits on the Gitlab but these do not provide any solution.
Along with this setup, I've added the forms module as a static include in my top-level template.
do you have a composer installation or an extension manager build up?
If a class is not found you may need to rebuild the autoloader information.
My error turned out to be caused by a corrupt installation. I've had to upload the file AddHmacDataConverter.php in the following path /public_html/typo3/sysext/form/Classes/Domain/Configuration/FormDefinition/Converters. A very weird error indeed.
For those that came here with the same error, make sure to check that folder. Apart from that add the news as a static inclusion in your top domain. You could also follow #Bernd Wilke's idea which s to disable the extension, clear all system caches (and additionally remove typo3/temp/autoload and then active the extension again.
I updated PHP 5.6 to 7 and MySQL 5.5 to 5.7.
Everything was fine in the older versions, however since I updated the server some plugins such as: Custom 404 page, gregorian2jalali face problems. Some pages goes blank and the Inspect Element, Console section nothing shows. up. For example, if I activate gregorian2jalali plugin, User Profie page doesn't show up.
Also in the Custom 404 page plugin, the following error comes up in 404 pages:
A Question2Answer database query failed when generating this page. A full description of the failure is available in the web server's error log file.
There was a related question for an earlier problem here: When adding page link, database query error occurs.
In the Apache Error Log, a message similar to this message comes up:
PHP Question2Answer MySQL query error 1146: Table 'qa.qa_options' doesn't exist - Query: (SELECT 'options' AS selectkey, title, content FROM qa_options) UNION ALL (SELECT 'time', 'db_time', UNIX_TIMESTAMP(NOW()))
Also, there was an earlier problem here at this question: is there a way to manually create the database tables ?
Now that the plugin is not updated, how I can fix this problem ?
Thanks
Q2A version: 1.7.4
There are two possibilities I can think of:
You are using a different table prefix (e.g. abc_ instead of qa_) in your qa-config.php file, and a plugin is putting qa_options in their SQL queries instead of ^options as they should (which automatically adds the correct prefix).
Or, you are using the unstable 1.8 version from GitHub which currently has a few issues regarding plugins. If so, make sure you're using the stable 1.7.4 version that you get from the main Q2A site.
I've updated a typo3 website from 4.5 to 6.2.9. Now the issues with old extensions are fixed. But now I'm facing an issue with real url extension [ver.1.12.8]. If it's disabled the front end is rendered with no issues. When the extension is enabled it shows this error
#1294587214: Configuration Error: 404 page "D:/Xampp/htdocs/project125/404-melding.html" could not be found.
Please help...
It appears, that you have the following value in your LocalConfiguration.php
[FE][pageNotFound_handling] = READFILE:D:/Xampp/htdocs/project125/404-melding.html
With this configuration, TYPO3 handles a pageNotFound event by displaying the content of the file configured (in your case D:/Xampp/htdocs/project125/404-melding.html). When the file can not be found, TYPO3 throws an exception with the code #1294587214.
Try to check, if the configured 404 HTML page exists in your filesystem and if not, create it. For further debugging purposes you could also set pageNotFound_handling to "true" or "1" to show an error message instead of an individual 404-page.
Also make sure you clear all caches and also the RealURL encode/decode cache.