Typo3 crashed after installing extension and now can't access live site or backend: Parse error: syntax error - typo3

As the title says. I was working on my typo3 site and tried installing the mmc_slideshow extension from the typ03 website. After clicking install an error appeared and now i can no longer access the live site. When I try to look at the /typo3 backend it is just the same error. It looks like the site is wiped. Is there anything I can do to get it back? I was able to see the files by looking into /typo3conf but it doesn't give me any editing options. The only thing i can think of is getting in through the hosting server.

Aside from the editing of typo3conf/PackageStates.php, which Mathias mentioned, you may need cleaning the cache (I don't remember the folder for sure, something like typo3temp/Cache/Code/? In doubt you may delete everything from /typo3temp/.)
Another option could be the Install-Tool where you might be able to disable failing extensions.

Related

"Source file could not be read" error when exporting database

I made a draft of a Wordpress website on localhost using XAMPP. I made a database for it using MySQL. I'm ready to upload to BlueHost. I understand that means I need to save the database as a single .sql or .sql.zip file.
I keep getting the "...\UAywaMh-.sql.part could not be saved, because the source file could not be read" when I try to turn the database into an .sql file that I can upload to BlueHost. BlueHost help says that the problem is not on their end. I've tried it in Firefox and Chrome. Chrome says "couldn't download."
I did leave the "New template" and "Existing template" fields blank. Is that it?
I know the name of the database I created and I was able to find it easily in https://localhost/phpmyadmin/ I don't think I have the wrong one.
How do I fix this so I can get my website live? Thanks!
UPDATE: On GitHub, someone described the same problem and said that patch #17447 fixes it, but I can't find the patch anywhere. https://github.com/phpmyadmin/phpmyadmin/issues/17445
UPDATE: A GitHubber responded! Turns out the answer is to update phpMyAdmin to version 5.20 or later! The first time I did this, I couldn't log in, but the trick is to copy over the config.something file!
Posting this so anyone in the future can find the solution.
The problem ended up being fixed by https://github.com/phpmyadmin/phpmyadmin/issues/17445 which was fixed in phpMyAdmin 5.1.4 and 5.2.0. It seems there was a related problem in PHP https://github.com/php/php-src/issues/8218 that caused download issues with some browsers.
Upgrading to the latest phpMyAdmin release was the solution.

Cannot access TYPO3 Backend after config change

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.

Typo3 broken: Frontend / Backend blank pages and no errors even after restoring backup

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.

Umbraco & goDaddy| error when trying to work with Umbraco back office

Like the header says I am getting an error when trying to work with Umbraco(6.2.1) back office
This is the error:
I already talked with goDaddy support, they says everything is OK from their side.
I flowed every "tutorial" I could find regarding this.
This is an error I am seeing in Goggle Chrome Console:
I am now clueless about what to do next.
*every help will be much appreciated.
This is the config folder:
This is the -- file -- it self
The error says you have an incorrect TinyMCE configuration. It will be a problem with that component and not the host. There is a [Umbraco support ticket] which suggested this may be fixed in release 6.2, but also a [forum post] where its said this could happen in all versions, when a style-sheet which is registered in the database is deleted.
Are you sure all the files are present in the deployed /config/ folder? Check that there is a /config/tinyMceConfig.config file present.

Permission error media TYPO3 6.1.0

I've got a Problem i can't upload any Media files in my Typo3 Backend.
If i choose a file in the Element browser I get a Internal Server Error 500, If i use upload i get this Error: Link Error
I also can't see the Thumbnails
I made the Files tyo3conf, fileadmin, typo3 and typo3temp with 777 access.
Imagemagick is also running and shows me all Test images.
Can anybody help me, I dont't know what do do.
The TYPO3 Version I use is: 6.1.0
I get a Internal Server Error 500
Have a look in your TYPO3 log accessible by the "log" backend module. If you can't find something there, get access to your vhost error log from the webserver. Usually, some sort of view capabilities are provided by some hoster control panels. Since it is a server error, you usually have to check the server log.
I also can't see the Thumbnails
Check your install tool again and play with the different options there. Also check that, in install tool > basic configuration, you have set the default paths (maybe let the install tool search again). You may see the test images, but if they're not generated correctly or display warnings, it may not work correctly.
Generally said: It is not really programming related, so IMHO not a fit for stackoverflow.com. Ask for help on irc.freenode.net in the #typo3 channel, this may be more helpful.