Project

General

Profile

Actions

Bug #57356

closed

After upgradation (from 4.5 to 6.1.7) page media (images) missing

Added by Prem S.G about 10 years ago. Updated over 9 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2014-03-27
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
6.1
PHP Version:
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

I've transferred a Typo3 installation to the new host And Upgraded it to the
latest version (from 4.5 to 6.1.7).

steps performed are:

Copy files and exported database from old host
uploading files and creating database at new host
changing config to match new hosts database settings
upgrading typo3 installation to latest version (at that time, current version is 6.1.3)

At this point pages in the frontend where missing images.

Checks I have performed:

folder permissions
uploads/fileadmin folders checked if they contained the missing images (yes, they did)
cleared db temp files as well folder temp directories

Still missing the images on the frontend as well in the backend under the media tab of the page settings.

note: We discovered change in the file storage of Typo3. I've upgraded the installation from 4.5 to 6.1.7. The images are moved from the /uploads dir to the /fileadmin/_migrated dir.

What else can I try? Please help...


Files

2014-03-28_12-01-46.png (55.3 KB) 2014-03-28_12-01-46.png Wolfgang Wagner, 2014-03-28 12:04
Actions #1

Updated by Prem S.G about 10 years ago

  • Project changed from TYPO3 Core to 2673
Actions #2

Updated by Nicole Cordes about 10 years ago

Can you see the relation in the backend? Have you checked the path to imagemagick/graphicsmagick in Install Tool?

Actions #3

Updated by Alexander Opitz about 10 years ago

Are the image tags in the source with the attributes width="0" height="0"? Then you should activate the filemetadata extension.

Actions #4

Updated by Bastian Bringenberg about 10 years ago

Uuuuuuhhhhmmmm... Just to be sure is this related to extension-forum or the Core? Because right now you are working on this ticket in my extension's forge project...

Actions #5

Updated by Prem S.G about 10 years ago

Alexander Opitz wrote:

Are the image tags in the source with the attributes width="0" height="0"? Then you should activate the filemetadata extension.

Some images are not even showing anything, it display like "<img width="" height="" alt="" src="">"
One thing i have noticed, is the images which they are not displaying in my local configuration
are from "typo3temp" in the live site
eg: <img width="144" height="96" alt="" src="typo3temp/pics/ec060aae43.jpg">

Actions #6

Updated by Prem S.G about 10 years ago

Nicole Cordes wrote:

Can you see the relation in the backend? Have you checked the path to imagemagick/graphicsmagick in Install Tool?

Yes "graphicsmagick" is installed and the path is correct in the backend, Some images are displaying correctly and the rest of the image's width and height are wrong.

Actions #7

Updated by Alexander Opitz about 10 years ago

  • Project changed from 2673 to TYPO3 Core
Actions #8

Updated by Alexander Opitz about 10 years ago

  • Status changed from New to Needs Feedback
  • Priority changed from Must have to Should have

Does the webserver have access to this uploaded files?
Did you copied the cache informations from your live server? If yes, clear all the caches.

Actions #9

Updated by Prem S.G about 10 years ago

Alexander Opitz wrote:

Does the webserver have access to this uploaded files?
Did you copied the cache informations from your live server? If yes, clear all the caches.

Yes now it works.. thank you Alexander Opitz
I copied the cache informations from my live server and also installed metadata extension

Actions #10

Updated by Wolfgang Wagner about 10 years ago

This problem still exists in TYPO3 6.2.0.

After upgrading from 4.5.32 to 6.2.0 I can't see images from page resources in the frontend.

HTML Source:

<img src="fileadmin/_migrated/media/headerimage4.jpg" width="0" height="0" alt="" border="0" />

The image exists in this directory!

I've installed the extension filemetadata, but in the "Metadata" Tab of the image width and height are 0, see attached screenshot.
Deleting the cache with "rm -rf typo3temp/Cache/" has no effect.

After deleting the old relation in the page resources and creating a new relation with the same image, it's visible in the frontend.

Actions #11

Updated by Alexander Opitz about 10 years ago

@Wolfgang Podbregar Can you take a look into http://forge.typo3.org/issues/46020 and try my described workaround please?

Actions #12

Updated by Wolfgang Wagner about 10 years ago

Hi Alex,

truncating the sys_file_metadata works!

Now the width and height attributes are empty in the HTML and the image is visible.

<img src="fileadmin/_migrated/media/headerimage4.jpg" width="" height="" alt="" border="0" />

This was only a small test website, but I think, truncating the database table is not the perfect solution, especially if DAM was used before and all metadata was migrated from DAM to FAL.

Actions #13

Updated by Alexander Opitz about 10 years ago

@Wolfgang Podbregar This will only help till next FE clear cache ... afterwards you will get the 0 back.
Did you take a look into the sys_lockedrecords?

Actions #14

Updated by Wolfgang Wagner about 10 years ago

Yes, you're right. Shit!

sys_lockedrecords had 2 rows and I cleared it in the install tool.

Now it has 0 records and the images are not visible. :-(

Actions #15

Updated by Wolfgang Wagner about 10 years ago

And now I even can not create a new relation, the image is not visible.

Actions #16

Updated by Alexander Opitz about 10 years ago

@Wolfgang Podbregar After you cleared you should empty the sys_file_metadata to get them rebuild.

Actions #17

Updated by Wolfgang Wagner about 10 years ago

Ok, I truncated the table again. After that the images are visible.

But then I cleared the FE-Cache -> images are not visible.

Actions #18

Updated by Alexander Opitz about 10 years ago

Would like to close this issue as duplicate of #46020 is this ok for you?

Actions #19

Updated by Alexander Opitz over 9 years ago

  • Status changed from Needs Feedback to Closed

No feedback within the last 90 days => closing this ticket.

If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.

Actions #20

Updated by David Bruchmann over 9 years ago

I had the same problem now with Upgrade from 4.5.37 to 6.2.9.
One reason is that by default paths are converted to lower case by default ( #55514 ) even the update wizard is using case sensitive paths.
So if #55514 is solved this bug is solved perhaps too.

Actions

Also available in: Atom PDF