2.1.4 Error I blew the horn too early !!!

[keyboard]

I Blew the Horn too early......I have three sites, the first two were successfully upgraded but the last Site that is important to me , has given me errors.

You cannot view this attachment.

You cannot view this attachment.

Please advise

RonP

[GL700Wing]

These errors are likely due to mods and/or custom edits having changed these files.

If you have the Automatic Attachment Rotation (and Resize) mod installed the errors in the Post.template.php file are likely caused by this mod - you must uninstall it before you upgrade to SMF 2.1.4.

I'll be releasing an SMF 2.1.4 compatible version of this mod shortly.

[Julius_2000]

I Blew the Horn too early......I have three sites, the first two were successfully upgraded but the last Site that is important to me , has given me errors.

You cannot view this attachment.

Please advise

RonP

You can click the scroll/pen symbol to the left of each error to see what it's referring to. That way, you can compare your current file with an untouched original one and see what's missing or changed.
Sometimes small edits can prevent the update from recognizing the to-be-changed item (in my case I had inserted a line of code while everything else was identical).
If you can identify missing code and its position within the php/css file, you then are able to just copy & past the required code to your custom file and then run the update validation again (refreshing your page).

[Steve]

@keyboard - you've been around long enough to know that your topic title should reflect what your problem is.

[Aleksi "Lex" Kilpinen]

Just said this in another topic, I'll just quote myself

cron.php is a file that should be there already, before the update. If it's not there, something is wrong.
You can probably fix this by downloading the 2.1.3 package, and uploading the missing file in place, before running the 2.1.4 update. But if I were you, I'd be wondering what happened to it?

EDIT:
cron.php shouldn't really be touched by the mods mentioned, so simply uploading a clean 2.1.4 version after the update should work just as well though.

[keyboard]

@keyboard - you've been around long enough to know that your topic title should reflect what your problem is.

A bit harsh !!!!

[m4z]

What did you find harsh? Mentioning your age, or the very polite hint that your utterly useless subject completely ignores not only our basic rules for posting here but common Netiquette as well?

You might as well have written "my forum doesn't work" which is basically true for every thread in this board.

A more useful subject would have been, for example, "2.1.4 upgrade shows errors for cron.php and other themes".