I did an upgrade from Typo3 4.5 LTE to 6.2 LTE, following the instructions found here: stack overflow
Now during the process of using the Upgrade wizard the Excepiton #1314516809 occured.
Then I went to the db using my php-myadmin and corrected the CaseSensitive-Value as recommended here:wiki.typo3
but the error stays. Rereading the code i realized, that the files, which could not be found, had doubled file extensions like
File /_migrated/RTE/RTEimage.jpeg.jpeg does not exist.
How can I get rid of them?
Maybe this will help.
Migration of RTE images
You must modify the database table sys_file_storage and remove the image entries which cause problems. The images of the migration folder should not remain here.
Related
I am experiencing a problem with the Productcomments module which I am using in a custom module and I cannot figure out how to fix it. The problem is with the star rating in the Productcomments form itself. This form works perfectly in a localhost environment - see images 1 and 2, but not on a live server - see images 3 and 4. On the live server it is showing no stars, just radio buttons, and no delete button for removing the stars.
Form as it looks on WAMP
Code from Chromes Inspect for WAMP
Form as it looks on Live Server
Code from Chromes Inspect for Live Server
Disabling the link to the following 2 js files recreates the problem on the local server which would suggest that the problem lies in the links to these two files on the live server, however I have checked all links to these files and they are correct, as are the permissions for these files.
jquery.rating.pack.js and productcomments.js
Occasionally when I clear cache under Advanced Parameters > Performance I get the following error message:
Fatal error: Uncaught --> Smarty: unable to write file /home/productm/public_html/cache/smarty/compile/10/e2/20/wrt5cbbb0747109d3_91450142
<-- thrown in /home/productm/public_html/tools/smarty/sysplugins/smarty_internal_write_file.php on line 46
This problem applies to all 1.6 versions of Prestashop tested.
Any suggestions on how to fix this problem would be appreciated.
Thanks
Kathleen
The error code you've got from clearing cache is linked to permission problems.
Here's probably a duplicate of your issue: How to fix erorr "Fatal error: Uncaught --> Smarty: unable to write file"?
Check that your prestashop files are set to 644 and folders 755 permission. (not just the js files you've mentioned).
Also if you manually moved the module to your live server(ftp), check the ownership of those files.
Edit:
I'll add this to the answer since the permissions didn't fix your problem.
looks like you have a prestashop bug going on with the JS (Synchronous loaded scripts)
here's a patch to fix that, maybe it fixes your original problem.
https://github.com/PrestaShop/PrestaShop/pull/6749/commits/73fd8dbed9f413a70f7d04fc4badd48f00ca501a
Refer the raised jira issue in below link .
https://wso2.org/jira/browse/IDENTITY-4633
Any solutions for solving this issue..,
We tried to temperorly solve this issue by editing sqlscripts.java file by downloading it from github, compiled it and tried to pack in same jar file (using winzip, as jar files are zip finally).
As part of the change we had removed TOKEN_SCOPE column from relevant sql query, but still error in log describes 'invalid column TOKEN_SCOPE'
Kindly suggest to make any further changes or share me the jar file.
I am using wso2 identity server v5.1.0
Thanks.
This issue seems to be already reported in https://wso2.org/jira/browse/IDENTITY-4532
This issue is already fixed in 5.2.0 which will be released soon. You can try the 5.2.0 beta from https://github.com/wso2/product-is/releases/tag/v5.2.0-beta
You can find the fix from the PR in the jira I have pointed.
I've performed an update from typo3 4.7.20 to 6.2.15. The process worked fine and there were no critical errors while running the install tool.
The frontend looks fine but the backend is broken:
I've removed all uncompatible extensions before I run the update. I've also checked all settings in the installationtool und deleted the temp/cache folder first.
I've got the feeling that the error is caused by the TemplaVoila! extension, I'm using v. 1.9.8. Firebug does not shows any error.
Does anyone had a similar problem and have already solved it?
Thank you very much!
I have come across this one multiple times. More often it is because there is a broken TBE_STYLES. I suggest you look around for $TBE_STYLES in your typo3conf folder and disable it for the time being. Most likely it will be in the extTables.php or some other file which is included dynamically.
seems BE is working, but you css does not got loaded.
check your 'web inspecter' to see if you get errors on loading CSS.
clear your cache (remove everything in typo3temp) and try again
I've written a sample c file which includes Xm/Xm.h. When compile it, I have the following error, "fatal error: Xm/Xm.h: No such file or directory"
I'm using AIX 7.1. What package do I need to install to fix this problem and where can I find it? I was not able to find anything online regarding this issue. Thank you.
I just got the same error message.
You need to install (with installp on Aix):
either openmotif (and openmotif-dev)
or lesstif2-dev (smaller then openmotif, and can be enough)
(as mentioned in this answer)
When I am trying to access my django site, it appeared the ImproperlyConfigured error say that "Module "django.template.loaders.filesystem" does not define a "Loader" callable template source loader".
I use Bitnami Django Stack and this is not the first time I installed it, so I think that there is the conflict between the old and new one somehow. I tried to clean the previous installation many times but it still be the same.
Sounds like you're trying to run the site on an older Django version.
In the settings.py file try 'django.template.loaders.filesystem.load_template_source' instead of 'django.template.loaders.filesystem.Loader'. The Loader name was changed in more recent versions.