I have updated my TYPO3 from 6.2 to 7.6.
Now many, but not all, images in the frontend and backend are displayed very large.
I emptied all caches. processed folder deleted.
What else can I do?
Related
I have added a product from magento admin and uploaded image for that product. Images are showing in backend but not showing in frontend.
I found that the image cache folder for thumbnail,base and small is not created under pub/media folder.So that images are not showing.
I have tried all the magento possible command to fix this but no luck.
Did you check the permission on the folder? The current php user has to have the right to write inside the folder.
In a TYPO3 6.2 site that was upgraded from 4.5, the "Ref" column in the file list doesn't provide accurate data.
For example, this image is definitively being used on a page, but the reference is not shown in the backend:
I have run the File Abstraction Layer: Update storage index task in the scheduler and updated the refindex several times - no change.
What can I do to make the references display correctly?
Conclusion of comments to a question:
After a migration from pre-FAL installation (TYPO3 < 6.x) all used images, that were located in /uploads/pics or /uploads/media are moved to /fileadmin/_migrated/ folder.
So, if your image in "Filelist" is reported as without references, then it means, that it probably is.
Be aware, that if you have extensions, which are not FAL-aware, then a file still can be in use, but no usage counter will be shown, becasue files are referenced not through FAL (db), but via filesystem.
At the moment of writing, I don't know any tool, that can help to migrate 'internal_type'=>'file' to FAL. If someone finds it, please, add it here in comments or as separate answer.
I am new to TYPO3 and got a problem. I have an existing website (6.2) and an old site (4.5).
Problem is that the old site has a lot of pages which should be migrated into the new site. The existing pages of the old site contain only regular content records. I want to avoid to copy hundreds of pages manually.
My idea is to upgrade the old site from 4.5 to 6.2. And then somehow copy the existing branches/pages eg. with help of sql? Does someone has experience with it?
If this might not work is it possible to copy at least the structure of the branches/pages? Means the content needs to be copied manually but at least page title, url etc. can be copied by sql?
All of a sudden one of our sites has developed an issue with TinyMCE, specifically it seems, in relation to the advimage plugin.
When trying to browse the image folder via TinyMCE I get an alert with one of these errors:
In Chrome I get:
2can't process ajax,TypeError: Cannot read property 'responseText' of null
In Firefox I get:
2can't process ajax,Invalid XML structure
Nothing has changed on this site for a good few months.
We have upgraded to PHP 5.4 very recently, but I don't see why that would be related.
This could be an issue with overly large images in the plugin's upload directory.
On each request, the advimage plugin scans the upload directory (set in your config) and generates thumbnails of any images it finds in there, then sends a list of images off to the client in the form of JSON or XML. If an image is too large to process, (low server memory or something), then the process quits and doesn't return any JSON/XML, hence the seemingly unrelated error message.
Prune any images over 1MB from the uploads directory. You may need to flush the cached thumbs as well. To stop your users/admins from uploading huge images, set an upload limit in the plugins config.
I have take over the management of a TYPO3 webpage, and Ive realized that everyday that goes by, it grows 1GB in CSS and JS files alone, "merged-ffff2d33c1ce910940054845fe400023.js" and so. Right now my compressor folder is 15GB big. It's huge!
It seems as if the CMS made a cache version of the CSS and JS with each page hit, but I'm just guessing as I have no idea of what's going on in this folder.
I've compared the files on each subpage, and while some commonalities are found, there's still many lines of difference.
How could I fix this?
I had the same problem when I set
concatenateJs = 1
concatenateCss = 1
compressJs = 1
compressCss = 1
in my typoscript. The problem is that TYPO3 seems to have a bug in compressing the JS and CSS files. I tested with 6.2.10.
With every request from every user/browser TYPO3 generates a new CSS file in typo3temp/compressed every day.
Deactivating compression
compressJs = 0
compressCss = 0
solves the problem and TYPO3 always delivers the same cached CSS file.
I have found that the CSS genereated by CSS Styled content is actually aware of which elements are on each page. So if one page has an image with text on the right, the needed styles for this is included, and if another page does not have an image with text on the right, this CSS is not generated. This results in the CSS actually being different on almost all pages, resulting in many merged CSS files.
I'm missing an option to just include all the CSS, not matter if its used or not. This might create a substantially larger CSS file, but at least it will be the same file on alle pages, and thus cacheable in the browser.
I would start to compare javascript files merged.
Can you tell me what is the difference ?
For example there can be a case when some javascript is generated with page id like
<script>
var pageId = 77;
</script>
If there is option turn on to move inline javascript to external file then this will be different for each page and finally merger will create new merged version for every page.
So the most important question for now is what is the difference beetwen merged files.
EDIT: The solution for you would be to remove all third part extensions. Clear the /compress/ folder. Then install those third party ext one by one and see which one is causing the problems.