Jump to content

Invision Community Blog


Managing successful online communities

Mark
Sign in to follow this  
 

Auto-Upgrader

Last year, we added an auto-install/upgrade tool into our client area. The tool would upload the latest version of the IPS Community Suite to your server automatically.
The way it worked was after submitting the request, you were entered into a queue, and a program on our server uploaded the files, and emailed you when it was done so that you could run the upgrader script. It normally took about 30 minutes.


30 minutes is pretty good. For someone without the technical knowledge to upgrade, it's a great alternative to asking for a support agent to do the upgrade for you (especially just after a release when everyone is doing just that). However, many users still prefer to do the upgrade themselves (after all, if you can download the source files and upload them to your server in the same time, what's the point?).


We decided we should try and get that time down. We also wanted the process to be much more seamless - so you click "Upgrade", get a loading screen, and then are taken immediately to the upgrade script when it's done, rather than waiting for an email.



Interested to see how fast we managed to get it? Take a look for yourself:
Watch Video




In addition, the system can now handle communities that have renamed their admin directory seamlessly without issue (it previously reset to /admin), and the system will automatically detect which encoding of IP.Nexus to use for your server, if applicable (previously it would only use Zend).




We really hope the Auto-Upgrader will provide a much easier way for you to keep your community up-to-date with the latest features and enhancements.


If you've not already upgraded to IP.Board 3.4, why not go and try it out now? To access the tool, simply go to the Purchases area of the client area, select the community you want to upgrade and click the big "Upgrade Now" button.

Sign in to follow this  

Comments



Recommended Comments

sounds interesting... is there a way to put the staging-area also in there?

 

I'd like to run this against my staging area and test everything out BEFORE upgrading production.... to see if everything worked out fine

 

How does this handle with non-standard templates and adaptions of css-stuff... is the template merging included here?

Share this comment


Link to comment
Share on other sites

It runs off your license URL so it can only be used for your live site.

 

It's exactly the same as doing an upgrade manually so just like normal you'd use the template merge center after the upgrade.

Share this comment


Link to comment
Share on other sites

the license includes one non-productive installation.... so is it possible to implement it like that, to have two URL's for the staging environment?

 

I'd like to avoid uploading it manually in staging and then doing it in another way in production.... it's crucial from my point of view, to do it the same way

Share this comment


Link to comment
Share on other sites

I was going to have a look but get this error... ;) something to do with the lifetime licence?


Fatal error: Method ipsManageCommunity does not exist in skinClients in /home/invision/public_html/clients/admin/sources/classes/output/publicOutput.php on line 3992

Share this comment


Link to comment
Share on other sites

I was going to have a look but get this error... ;) something to do with the lifetime licence?


Fatal error: Method ipsManageCommunity does not exist in skinClients in /home/invision/public_html/clients/admin/sources/classes/output/publicOutput.php on line 3992

 

Odd... I can't imagine how that would happen. Give it another try now.

 

 

 

Auto-Upgrader not upgrades basic(master) skin images ;)

 

After it I was compelled to manually upload files. 

 

I'm not sure what you mean - it uploads the default skin images same as everything else.

Share this comment


Link to comment
Share on other sites

You need make filling in your ftp details easier. i.e. for every entry have some help available. For example on the "Port" information you could say "Usually 21". By "Path" what do you mean? Is that the name of my forums folder?

Share this comment


Link to comment
Share on other sites

You need make filling in your ftp details easier. i.e. for every entry have some help available. For example on the "Port" information you could say "Usually 21". By "Path" what do you mean? Is that the name of my forums folder?

Maybe a request (in feedback forum) where there's a link to use the auto-upgrade feature and when it's clicked, it'll provide the (current) path, so that it's already filled in.

Share this comment


Link to comment
Share on other sites

I'm really not sure how to fill in the information. A sample would be awesome. For example, do I include the trailing slashes? For the server address, do you want the IP address? Do I include the http:// or ftp:// parts?

Share this comment


Link to comment
Share on other sites

Blowed if I can get the upgrader to work. I'm testing it on my test forum. Despite me filling in correct ftp details (copied from my ftp client) it says it can't login.

 

Ditto what bzk says. You need to provide a sample of how to fill in the information.

Share this comment


Link to comment
Share on other sites

Working now that I've entered /public_html/board

 

The problem now is the upgrader says the url for the licence doesn't match the url on file. Okay I can change it so that I can upgrade my test forum but I'll be wacked $15 to change it back when I want to upgrade my active forum. No thanks. Maybe when I come to upgrade my active forum to 3.4.1 I'll give the upgrader a bash, however I did really want to try it out on my test forum first (same server just different folder).

Share this comment


Link to comment
Share on other sites

You fill it in exactly as you would in your FTP client...

 

Server: example.com

Username: foo

Password: bar

path: /public_html

Thanks. That helps. But... Still not working. I'm getting an error message that says it can't find the FTP server.

 

And there's a bug or something--I enter port 21 in the Port field, and then submit. An error is displayed, but then the Port gets changed to /public_html/

 

So I enter:

 

Path: /public_html

Port: 21

 

But after the error is displayed, I see:

 

Path: /public_html

Port: /public_html

 

And it's helpful to see an example because of things like leading and trailing slashes, IP addresses, etc.

Share this comment


Link to comment
Share on other sites

To anyone asking "does this over write CSS etc"

 

All this is doing is uploading the new files to the server.

 

You still need to run the upgrade script and revert any changes etc like you would have to usually.

 

My internet connection is pretty poor, so would this speed the process up? As it would be using IPS's upload resources instead of pulling it from my local machine?

Share this comment


Link to comment
Share on other sites

To anyone asking "does this over write CSS etc"

 

All this is doing is uploading the new files to the server.

 

You still need to run the upgrade script and revert any changes etc like you would have to usually.

 

My internet connection is pretty poor, so would this speed the process up? As it would be using IPS's upload resources instead of pulling it from my local machine?

 

Exactly, yes :)

Share this comment


Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Add a comment...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...