Thread

We have recently upgraded an EE 1 site to EE 2.2.2. The site had a lot of channel posts (500+) which had file attachments. This was via a simple file attachment custom field. On upgrade EE has lost the link to the attached files. The links to the files simply do not appear on the front end pages and if I go and edit the post in the CP the attached file does not show.

However if I go into the exp_channel_data table I can see that the file name is still stored in the field in the database and the files appear in the new file manager now I have synced them.

Is there an easy way of resolving this one. We don’t want to go in and manually edit 500 posts and re-link the files.

Hi, sourcedesign.

If you view the source in the entry, what shows exactly?

Hi, sourcedesign.

If you view the source in the entry, what shows exactly?

Hi Sue, if I view the source of the page it is just an empty a tag:

<ul>
<li><a href="http://">Competition results</a></li>
</ul>

The EE code for the above would be quite simple:

<ul>
<li><a href="http://{member-news-attachement}">_{if member-news-attachement-label <> ""}_    {member-news-attachement-label}_{if:else}_    {member-news-attachement}_{/if}</a></li>
</ul>

Let me know if you need an further info.

Hi, sourcedesign -

The site had a lot of channel posts (500+) which had file attachments. This was via a simple file attachment custom field.

Was this using a custom extension of some sort?  what type of custom field was this in EE 1?

Thanks!

Was this using a custom extension of some sort?  what type of custom field was this in EE 1?

Hi Lisa,

Yes, we were using Mark Huot’s File Extension for EE 1. I can’t find a direct link to it now online.

Our upgrade of this site from EE 1 to EE 2.2 was problematic nearly all of this stemming from our use of third party extensions and getting everything to work with the new file manager.

In the end we couldn’t see an easy solution so we synced the files are re-attached them all manually :-(

Ah yes, that does explain it.  unfortunately there was not an automatic way to upgrade from using Mark’s extension (which had long since been no longer supported, for years actually) to EE 2.

At this point, are you all set? I am sorry you had to go through that. :(

Ah yes, that does explain it.  unfortunately there was not an automatic way to upgrade from using Mark’s extension (which had long since been no longer supported, for years actually) to EE 2.

At this point, are you all set? I am sorry you had to go through that. :(

Thanks Lisa. Yes, it is sorted. Onward and upward!

Good to hear it, sourcedesign!  Please let us know if you need any further assistance.