I tried to update TYPO3 website from 7.6.x to 8.7.x. When I run "Execute database migrations on single rows" in update wizard I get an error:
Oops, an error occurred!
Child record was not processed, reason "[1.0.-1]: [newlog()] Localization failed; There already was a localization for this language of the record!"
More information regarding this error might be available online.
I think this problem is caused by t3blog extension and translated content element in posts. If I ignore this error and run other wizard steps all content is shown on website, but not translated blog posts content elments.
Anyone an idea how I can solve this?
Thanks!
Martin
Running first "Fill translation source field (l10n_source) " and then "Execute database migrations on single rows" seems working
Related
Why can't you see exactly where the error is thrown with Typo3? Like with Laravel. When an error is shown it usually also shows on what PAGE CLASS or FUNCTION that error is made....
Is it possible, to change that? With an extension or something?
Please see the documentation about Error and Exception Handling on how to configure this to display all error details locally but only show a human readable error on production.
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.
I am working on a project where client requires me to beautifully display error 500 with stacktrace etc.
So, I checked the Error Controller and made a nice fancy error page in corresponding views/script
The problem is, how do I test it?
Whilst working on the project, I cleared error on every page and there is no way I could generate it again. Also, I am using doctrine and I remember "echo-ing" the entitymanager array but, I cannot trace the location.
How would I custom generate error 500, "keeping it real"?
PS: I tried htaccess thing and trust me, it throws apache error and not zend 500.
It was pretty silly but, finally found it.
All I needed was to mis-spell a dql tablename on any page where I use querybuilder.
I recently upgraded our SugarCRM CE form 5.x to 6.2.6. I had some uphill experience but I overcome everything except one issue.
The following error appears in the "Email Address" area on Contact, Opportunity and other similar pages.
Warning: Smarty error: unable to read resource:
"include/SugarFields/Fields/Base/detailViewFunction.tpl" in
/home/campusre/public_html/sugar/include/Smarty/Smarty.class.php on
line 1095
I did a search on SugarCRM forum and I found only one similar thread that was old and not answered. I also contacted our hosting company to check if this problem is related with the file or folder permission but they confirmed that it is not the problem in this case.
I am a developer but didn't do any SugarCRM and Smarty development before. I am investigating the code by my self but without success so far.
Any suggestion will be highly appreciated.
Thanks in advance.
unable to read resource: include/SugarFields/Fields/Base/detailViewFunction.tpl
This usually means that incorrect permissions are set on this file or that the file doesn't exist. However, in this case it looks like a casing issue. The file is actual camel case and named DetailViewFunction.tpl. It looks like you are running into a case-sensitive issue. My initial guess is that it is due to an old module or piece of code from 5.x.