it happens on each every page . I have no idea about this error. Any help?
The column SiteName was removed in v9. Here's an article talking about it. Here are the release notes for v9. So you'll have to log into the Admin site and to to Page Templates and modify your listing repeaters in there to remove the SiteName column.
UPDATE
What you can do to get a list of templates which have SiteName is to run a SQL script like so:
SELECT *
FROM CMS_PageTemplate
WHERE PageTemplateWebParts like '%sitename%'
This will give you a list of templates which have webparts that the property or value of SiteName in them.
Did your database upgrade show any errors? Maybe check your version in the database vs your site structure and see if they match. I think just from the looks of it, your database upgrade didn't complete or had an issue. You could try rolling back to your backup and reupgrading maybe by running the upgrade query on your database.
Related
so i was on vacation for 5 Days and when i came back our Website (Typo 3 - 7.6.25) was "broke".
If i try to go on the page i get the following Error:
#1205414233: No suitable request handler found.
TYPO3\CMS\Extbase\Mvc\Exception thrown in file
/html/typo3/typo3_src-7.6.25/typo3/sysext/extbase/Classes/Mvc/RequestHandlerResolver.php in line 83.
Neither me nor anyone else in my company changed something on the Typo3 Website in the past 5 Days.
I've tried to search for Solutions but neither of them helped.
Sadly we have no Backups (This will be Priority 1 after this).
I've also found a Typo3 Website talking about that problem here: https://wiki.typo3.org/Exception/CMS/1205414233
but i dont know where to include the code given by this Site.
Does anyone know what I can do with this Error?
Thanks.
first of all TYPO3 7.6.25 is from 13.03.2018. The last free release is 7.6.32 from 11.12.2018. There are many security updates since your version. If you buy ELTS you can download and install 7.6.41 ELTS (28.01.2020) Maybe this will help with your problem.
Other things you can check: Hosting Provider changes php version or mysql? I really think you should try update to TYPO3 8.7 and test again. Backup your site befor update.
It seems this can have different reasons. In my case (in TYPO3 8.7) the problem was triggered from comments in TypoScript. I've used a (valid!) multi line comment:
plugin.tx_myplugin {
settings {
firstsetting = 1
/*secondsetting = 2
thirdsetting = 3*/
}
}
In the "TypoScript Object Browser" there was a warning, it seems TYPO3 had problems parsing TypoScript due to this comment.
I have created an identical copy of our production instance to my local environment running XAMPP and I am trying to do the following:
After upgrading Moodle from 3.5.10 to 3.6.8 and restoring all plugins etc. I am unable to login. Before upgrading to 3.6.8, I had already performed the following upgrades,
3.4.1 -> 3.4.9
3.4.9 -> 3.5.10
and everything worked fine during those 2 upgrades. I followed exactly the recommended upgrading method as described in moodle's docs.
After successfully upgrading to 3.6.8, I successfully passed the step about the server requirements for the correct php mysql and db versions, I then successfully passed the next step as well for upgrading the database and made sure that all the plugins are fine and had no errors (just some warnings about a few plugins that can be updated to newer version) and after that step finished too, I then got back to the /admin/index.php screen asking me to login. That seemed weird to me because during the previous updates, it never asked me to login after completing the upgrading, but I said, ok. i'll just login. So after trying to login i am constantly getting the message "Invalid login, please try again"
I have tried almost anything here and by anything I mean the following.
First of all, I checked my hashed password in the local database and it is exactly the same with my hashed password in production database.
I then read an article that from moodle 3.1 the logintoken was introduced and since we use the mb2nl theme, I supposed that I just have to add the new input hidden field for this logintoken to the login form but the field was already there and again that was not the issue.
I am at a point where I cannot think of what else might be wrong and I am stuck.
A few more information about our whole setup, we have a Joomla website and our moodle users are actually coming from Joomla, Therefore we use a plugin named Joomdle which connects these 2 CMSs. Our users register to our Joomla website and the Joomdle plugin sends the credentials to moodle and the user is being created to the moodle CMS as well and an entry is being created in the moodle's "user" table. The difference is that moodle generates a different hashed password from the hashed password that joomla does. Anyway, there were no problems at all with logins or anything else since I tried logging in with multiple user accounts in moodle and all worked fine, before upgrading to version 3.6.8.
This is not a Joomdle issue since I already checked this by completely removing Joomdle and this is not the cause. This is probably coming from moodle core but since moodle has NO error reporting or logging at all, I really cannot understand what this is.
To exclude one more matter linked in this question, I already checked and made sure that moodle's password salt is the same both in production and local environments.
I am not sure what is going on here and this is why I desperately need some help from experts.
Solution:
I was able to solve this problem but forgot to come back here and give the solution.
The problem was that, as I said above, we are using the mb2nl theme and the theme's login form did not include the hidden input field to create the logintoken.
On my question above I write somewhere in the middle "I supposed that I just have to add the new input hidden field for this logintoken to the login form but the field was already there and again that was not the issue". I was looking at the wrong place. The login form that I was looking at, was the Moodle's itself login form and not the theme's login form.
I then found the login form in the theme's files and the logintoken hidden input field was indeed missing from there. I added it and then I was able to login normally.
Happened to me today. Executing the cron.php cli script trigered again the upgrade process and solved my problem.
After upgrading the existing v9 site to Kentico 10 I'm getting a security exception error when loading the site. The CMS admin however loads fine. I already added the FULL trust setting in web.config but it did not work. Any idea?
Problem, based on part that I can see and exception type would be in new SQL parser which was added in one of the hotfixes for v9 and thus it is part of v10.
You seem to be using one of the properties in a web part and than passing incomplete query via ##WHERE## macro. If a where condition is like {%CurrentDocument.DocumentID%} it is not a valid WHERE and whole property has to be complete SQL statement on its own, so it could be like DocumentID = {%CurrentDocument.DocumentID%}.
You can find a bit more in this thread:
https://devnet.kentico.com/questions/invalid-sql-query-error-on-a-page
Try load the template in the Admin UI pages application, then check the event log application, you should see the detail information about the SQL error. Most likely you have a SQL call that is trying to get some data from a column that's no longer there (through upgrade).
I want to update a TYPO3 Project from 4.1 to 6.2.9. In order to do that I need to upgrade it to find the most compatible extensions. So I've updated the TYPO3 to 4.5. Now the back end loaded and it shows some arguments that are printed. Also in front end it shows this error.
The requested page didn't have a proper connection to the tree-root!<br /><br />(Broken rootline (failed on page with uid 7))
I fixed this issue.
After going to Install tool. In DB Analyser there are so many tables are not properly indexed. After fixing that this issue has been fixed.
Truncate realURL-tables and clear Cache via InstallTool.
This works for me.
Is there any direct api to fetch a file entry by title with given folder id.
I have tried DynamicQueryFactoryUtil, apart from this is there anything to fetch DLFileEntries by title.
I believe DLFileEntryLocalServiceUtil.getFileEntryByTitle() is not there anymore in Liferay 6.1
In Liferay 6.1.0, I can see there is
com.liferay.portlet.documentlibrary.service.DLFileEntryLocalServiceUtil.getFileEntryByName(groupId, folderId, name), as I get from lib/ext/portal-service.jar
You can also see the official documentation here
I think you start by making sure you have the correct libraries imported
EDIT:
I guess that the parent folder and groupID are needed as more than 2 DLFileEntries can have the same title/name. If you need exactly 1 result, and giving only 1 attribute, you can use getDLFileEntry(long fileEntryId). If this doesn't help either, you should tell us some more on what you want to do , and what information you have available (except the title of course)
Liferay has a strange compatibility policy.
Seems like they renamed the getFileEntry to getFileEntryByName and getFileEntryByTitle to getFileEntry. The old and new getFileEntry both share the same singature, but the parameter name is different. :-(