Jump to content

Recommended Posts

Posted

After transferring attachments from the file system to Amazon S3, many thumbnails are out of date, even though the attachments were transferred correctly.

  • Could contain: Nature, Night, Outdoors, Astronomy, Nebula, Outer Space, Sky

Is there a way to rebuild them?

Posted

We would need to look further into this for you, however the access details on file appear to be incorrect or missing. Could you please update these details by visiting your client area, selecting the relevant purchase, then clicking "Review/Update Access Information" under the "Stored Access Information" section. 

We look forward to further assisting you. 

 

Posted

@Joel R thanks for the idea, now I tried it but it did not help

It seems that in some places the thumbnails still show the old address instead of the new CDN address

Posted

I've seen situations where people have manually linked to attachments by copy/pasting the URL.  If that happens instead of using the "Other Media" option (insert existing attachment) for example, it would not get updated.  It won't update links someone copy/pasted.  

Posted
4 minutes ago, adik said:

@Joel R thanks for the idea, now I tried it but it did not help

It seems that in some places the thumbnails still show the old address instead of the new CDN address

 

2 minutes ago, Randy Calvert said:

I've seen situations where people have manually linked to attachments by copy/pasting the URL.  If that happens instead of using the "Other Media" option (insert existing attachment) for example, it would not get updated.  It won't update links someone copy/pasted.  

As Randy mentioned, you’ll want to check those images to see if they’re attached. If they aren’t, more than not they were copied/pasted by URL so the system simply wouldn’t know of them. 

Posted

It makes some sense

Do you have any idea how to fix this problem? Any larger SQL database query? It appears in several places - topic / profile 'about me' / signature / PM etc

Posted

This would be outside our scope of support, I'm afraid. As manual URLs are handled differently and not associated in the software, it isn't really something the software is set to handle when the URL changes. A third party provider may be able to assist you with this custom update, if you wish.

Posted

I looked in the database and here is the result:

Post with the problem:

Quote

<img alt="image.png.f7ce5212b9066f2f8a5dbe2a9d512123.png" class="ipsImage ipsImage_thumbnailed" data-fileid="7971" data-ratio="46.68" style="height:auto;" width="392" data-src="<___base_url___>/uploads/monthly_2023_02/image.png.f7ce5212b9066f2f8a5dbe2a9d512123.png" src="<___base_url___>/applications/core/interface/js/spacer.png" />

Good post:

Quote

<img alt="tester.png" data-fileid="6096" data-ratio="150.80" style="height:auto;" width="332" data-src="<fileStore.core_Attachment>/monthly_2020_12/43551202_tester.thumb.png.91a4da4693e422cff50bf57ecb3fc15v.png" src="<___base_url___>/applications/core/interface/js/spacer.png" />

That is, instead of the "<fileStore.core_Attachment>" storage method, the default forum address is "<___base_url___>"

I will replace it manually in the database, but I am still curious if it is definitely the user's fault?

Posted

I would highly advise on following this up with our developer in your ticket and not touching anything beforehand. 

  • Solution
Posted

@Marc Stridgen the devil tempted me to try to do it manually 😈

UPDATE core_members SET signature=REPLACE(signature, '<___base_url___>/uploads/monthly_','<fileStore.core_Attachment>/monthly_');
UPDATE core_message_posts SET msg_post=REPLACE(msg_post, '<___base_url___>/uploads/monthly_','<fileStore.core_Attachment>/monthly_');
UPDATE forums_archive_posts SET archive_content=REPLACE(archive_content, '<___base_url___>/uploads/monthly_','<fileStore.core_Attachment>/monthly_');
UPDATE forums_posts SET post=REPLACE(post, '<___base_url___>/uploads/monthly_','<fileStore.core_Attachment>/monthly_');
UPDATE core_member_status_replies SET reply_content=REPLACE(reply_content, '<___base_url___>/uploads/monthly_','<fileStore.core_Attachment>/monthly_');

It came out fine. I marked for myself about 100 places where there was this problem, and everywhere is in good

 

Thanks to everyone for your help. The topic can be closed

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...