TYPO3: Wrong URLs after moving to new Server - typo3

I developed my TYPO3-Project using a local Vagrant-Machine. Now I bought some Webspace and wanted to migrate it there but I keep getting Errors.
Whenever I try to call the URL, TYPO3 is giving me the "Ops, an error occurred!".
I can, however go to the back-end and install tool and everything looks fine there! All the pages with all their content are editable.
Now for the weird part:
Whenever I try to open a Sub-Page from the Backend, It wants to load it with the base-url of my Dev-Server. I migrated the Database correctly and Installed the TYPO3-Installation accordingly.
So basically this is whats going on:
My development enviroment has its own Database and is working perfectly fine
I exported the Database via terminal and imported it via PHPMyAdmin to the new Hoster
I set up my TYPO3 Project and Changed the Localconfiguration.php
I added the new URL to the TYPO3 Project
--> Everytime I open a link I either geht the Blank Page with the "Oops, an error occurred! Code: 20171002194119799d9c1b" or it tries to open the wrong URL.
I used:
Homestead as my Vagrant Box
Composer to install TYPO3 and the extensions
Realurl (latest Version)
TYPO3 8.7.7
My RealUrl setup in my page.config looks like this:
absRefPrefix = /
tx_realurl_enable = 0
linkVars = L(0-3)
index_enable = 1
index_externals = 1
Thanks in advance! I know this is quite something to read but I've struggled for the last 5 hours with this problem and I don't know where to ask but here.

Did you changed the domainrecord?
Open the rootpage in list mode and modify (or add) the domain record to match the current domain.

Related

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 CMS 8.7 Jquery errors after moving site

Recently I've moved one of my development sites into production.
The following steps were taken.
Complete backup of both versions (4.5 & 8.7)
Removal of old version
Uploading new TYPO3 developed version
Updating database connection in the LocalConfiguration file
After doing all this and enabling the install tool I am able to login to my install tool but not into the backed. Both the install tool and the backend are giving the following error.
Uncaught SyntaxError: Invalid or unexpected token on Jquery. Various other errors also appear because of this. Included below is a screenshot for completion.
No file transfers failed and I am unable to login to the backend. I haven't done anyhthing to the database apart from setting it up
It's possible that file-compression was activated for JS- and CSS files which doesn't match the settings on the new server.
If you click in the browser-console on a file-link you get some output like this:
You can adjust the compression-level in install-tool but can see the value in the file typo3conf/localconf.php (for TYPO3 4.x) or typo3conf/LocalConfiguration.php (for TYPO3 8).
It might currently look like this:
$TYPO3_CONF_VARS['BE']['compressionLevel'] = '9';
and you can adjust it just to 0:
$TYPO3_CONF_VARS['BE']['compressionLevel'] = '0';
In the install-tool of TYPO3 4.5 the option looks like this:
The problems comes from the setup.ts or config file. Comment / uncomment these lines until it will work. Is usually the compression of js that is the problem:
#config.concatenateCss = 1
#config.compressCss = 1
#config.concatenateJs = 1
#config.compressJs =1

not open magento dashboard login panel after successfully install

I am install magento latest version and it install successfully but my problem is when i am try to open the dashboard then no one error but not show login panel like images https://imgur.com/7bTHEVd it show blank like image
Are you on Magento 2.3.0, this happened to me the other day ?
It looks like it's a bug with:
#/vendor/magento/framework/View/Element/Template/File/Validator.php:138
Change line 138 from: $realPath = $this->fileDriver->getRealPath($path);
to:
$realPath = str_replace('\\', '/', $this->fileDriver->getRealPath($path));
Please Note
- This is just a temporary fix to make it work on your local Windows machine, don't commit or push any of this code to production as it is editing the core files (not recommended)

TYPO3 8.7.1 backend Login not working

I have a plain naked TYPO3 8 lts installation.
But I cant login with the backend user.
Install Tool works fine
When I create a new BE user in install tool it does not work as well ...
any ideas?
Check in Localconfiguration the [BE][loginSecurityLevel] and change it to normal if it is rsa
For me the solution was deleting the cookies from the browser, then login form works good.
I ran to a problem where I couldn't login to backend, even if I had [BE][loginSecurityLevel] set to normal. Nether did it work on a unix system or windows. The reason I found out was, because the extension 'sv' was disabled (not in PackageStates.php array).
So I went to PackageStates.php and added following to the array:
'sv' => [
'packagePath' => 'typo3/sysext/sv/',
],
Before that happened, I downgraded TYPO3 from 9 to 8. I was able to log in first, but not the next day, after the first logout.
This extension contains core default services.
Use the Debugger for your browser, e.g. Firefox Developer, and check if an error is given there.
Loading failed for the <script> with source “http://www.my-typo3-website.de/typo3/sysext/core/Resources/Public/JavaScript/Contrib/jquery/jquery-3.2.1.js”.
If you copy and past the above url into a web browser, you will see this outpu:
The requested URL /typo3/sysext/core/Resources/Public/JavaScript/Contrib/jquery/jquery-3.js was not found on this server.
The file name jquery-3.2.1.js has been abbreviated into jquery-3.js!
It can happen that the jquery used by the login form is not included as needed. This can happend by a Rewrite rule in the .htaccess file which transforms the filename jquery-3.2.1.js into a smaller name jquery-3.js which will not be found, because it simply does not exist on the file system.
At least you should try out the original .htaccess file named "_.htaccess" which is shipped with TYPO3.

Content model is not working in 4.2.f

Okay, so I had a working content model and share config in alfresco community 4.2.e. I had to reinstall alfresco and I updated to version 4.2.f. When I start tomcat I can log into alfresco, but when I try to load share it takes like 10 minutes to load and when it has loaded and I try to login it says "not availible or wrong login" after 3 minutes.
Here is the content model: http://pastebin.com/2wMJe3YL
.And the share config: http://pastebin.com/n1YK6i60
--edit1--
The alfresco.log: http://pastebin.com/PaiAUv9n
The alfrescotomcat-stdout(date).log: http://pastebin.com/RZ4fVJ8G
In the 2nd log I noticed it says refused connection, can the problem be that I changed some ports on the reinstallation from alfresco?
-- end edit1--
Alfresco does work with no content model and share config used and Alfresco works with the standard content model and share config.
Thanks in advance.
Solution: The problem was that I thought that the reinstall of alfresco would be enough to change the ports and it is, but I forgot to add some code in MY share config. The code I mean can be found here: https://wiki.alfresco.com/wiki/Changing_Default_Port_Configuration thanks to: Gagravarr