Rc3 Upgrade Feedback thread...

Sort by date Sort by votes
Kier said:
How many people decompress on their local machine then upload the decompressed files, and how many upload the entire zip and then decompress via SSH right on their server? The latter is hundreds of times faster, if you know what you're doing.
Click to expand...

I have to upload the zipped file and compress on the server. I use Core Light ftp and it hangs too much to make it worth while.

I updated one of my sites and will be doing the other tonight.
 
Upvote 0 Downvote
Upgraded from RC2 to RC3. 12 minutes to upload uncompressed files via Filezilla, 45 seconds to run the upgrade script. ALL is good here!!

I like the way it closes my board without me doing anything. I thought there was a step out of sequence in the instructions - but NO. Must be a file-overwrite right at the beginning that does that. Neat!

And all my plugins still work - AWESOME!
 
Upvote 0 Downvote
All went well except that our entire color palette for all styles was reverted to the default on upgrade. :( Have to rebuild it...thank goodness for sticky notes with hex codes scratched on them!
 
Upvote 0 Downvote
Ati said:
Updating templates was not as easy as with vb. vb showed me what the differences were, and it was easier to apply the changes. With this upgrade, I remembered what my changes were, but I only have one add-on installed + one own "html wrapper". I plan to add a couple more add-ons... Updating then will become a nightmare... Are there any plans to make this easier in the future?
Click to expand...

As more template hook locations are added there will be less of a need for manual template edits when installing an Add-on.
If one is absolutely nescessary, the edit should be no more than <xen:include template="nifty_stuff" />, possibly wrapped in <xen:if is ="{$show_nifty_stuff}"></xen:if>, which makes re-appling a template edit very quick and painless, :)
 
Upvote 0 Downvote
Lawrence said:
If one is absolutely nescessary, the edit should be no more than <xen:include template="nifty_stuff" />, possibly wrapped in <xen:if is ="{$show_nifty_stuff}"></xen:if>, which makes re-appling a template edit very quick and painless, :)
Click to expand...

They are not big edits, but you have to remember where in the template they are. I think I'll have to make some notes about the changes for future reference. That'll be the best.
 
Upvote 0 Downvote
Ati said:
They are not big edits, but you have to remember where in the template they are. I think I'll have to make some notes about the changes for future reference. That'll be the best.
Click to expand...
That's what I do.

I have a file listing all of my template, phrase, css and core file edits.

Come upgrade time I just have to refer to that and reapply any edits for any reverted templates.
 
Upvote 0 Downvote
As a license holder, I would prefer an email advising me of the availability of a new release. I realize that right now, one is expected to subscribe to a thread (or is it a forum... I don't know) to be alerted. Will this be the policy going forward? If so, will it also be policy for receiving security release announcements?
 
Upvote 0 Downvote
Awesome-o said:
As a license holder, I would prefer an email advising me of the availability of a new release. I realize that right now, one is expected to subscribe to a thread (or is it a forum... I don't know) to be alerted. Will this be the policy going forward? If so, will it also be policy for receiving security release announcements?
Click to expand...

It is my experience that it's always best to wait a few hours before downloading the new versions. Of any software in general. That way if there are any major issues, they can be fixed by the time you download. Because of this, I think it is a really good practice that announcements of new versions are not sent out immediately.
 
Upvote 0 Downvote
Awesome-o said:
As a license holder, I would prefer an email advising me of the availability of a new release. I realize that right now, one is expected to subscribe to a thread (or is it a forum... I don't know) to be alerted. Will this be the policy going forward? If so, will it also be policy for receiving security release announcements?
Click to expand...
Emails will go out - for stable releases. Obviously pre-1.0 is a bit of a different situation, but most users shouldn't be upgrading to non-stable releases, so sending out an email isn't really the best idea. Users that are active are the more general target for non-stable releases.

The emails that go out won't be instant either. Security announcements would probably go out more quickly, but I'd expect to see a delay between a maintenance release becoming available and an email being sent out to customers.
 
Upvote 0 Downvote
Kier said:
How many people decompress on their local machine then upload the decompressed files, and how many upload the entire zip and then decompress via SSH right on their server? The latter is hundreds of times faster, if you know what you're doing.
Click to expand...

I always do it via SCP -> SSH -> UNZIP. I wish FTP was never invented. :)

By the way generating temporary HotLinks after validation will help us using WGET directly. :)
 
Upvote 0 Downvote

Similar threads

Paul B
  • Locked
General 2.3 discussion
11 12 13
Replies
242
Views
19K
Suzanne O
Suzanne O
Apt Irrelevance
  • Question Question
XF 1.5 Upgrading large forum from XF1.5 to XF2
Replies
10
Views
726
TheLaw
TheLaw
Jakkal
  • Question Question
VBulletin 5.x to Xenforo Question
Replies
5
Views
399
Suzanne O
Suzanne O
Chromaniac
  • Question Question
XF 2.3 Question about testing upgrade to 2.3
Replies
8
Views
569
AndrewSimm
AndrewSimm
Sanctum Staff
  • Question Question
XF 2.2 Locating a Troublesome Link
Replies
1
Views
224
AndyB
AndyB
Top Bottom