Forum

Notifications
Clear all

1.16 -> 1.17

4 Posts
3 Users
0 Reactions
21 Views
Posts: 20
Topic starter
(@alexbuckland)
Member
Joined: 6 years ago

Hi Stevland,

About to upgrade from 1.16.3 -> 1.17.1 and we use a number of plugins list below. I have seen several topics about problems with plugins and moving from 1.16 -> 1.17 do you have some upgrade recommendations I can refer to, to avoid problems?

We use:

Attachment Inline
Attachments on the filesystem
Password Manament Policies
Two Factor Authenticator

Our current setup:

osTicket v1.16.3 // osTicket-1.16.3-Awesome-101
PHP 8.0.25 // MySQL 5.7.39 // Apache web server

Thanks!

Alex. πŸ™‚


3 Replies
Posts: 36
(@nandor)
Member
Joined: 4 years ago

Hi,

I recommend a clean solution:
Before the upgrade, uninstall all extensions from the database and the plugin directory.


Reply
Posts: 20
Topic starter
(@alexbuckland)
Member
Joined: 6 years ago

Yep, all completed. So I:

Backed Up.
Put Cloudflare into Dev mode to bypass caching
Disabled and deleted all plugins
Followed the guide here: https://osticketawesome.com/installation-instructions/
Reinstalled new (but same) plugins using OSTicket wizard
Reinstated the custom logos.
Re-activated Cloudflare

All sorted, version 1.17.1! 

πŸ™‚


Reply
Posts: 1177
Admin
(@stevland)
Member
Joined: 2 months ago

Hi @alexbuckland,

The only problem with plugins was the Attachment Inline/Preview plugin in the first release for 1.7, but that was resolved in the next release.

I doubt you would have had any trouble without taking extra precautions, but thanks for reporting back and sharing your solution.

I've never used Cloudflare. Is it important to put it into dev mode when upgrading osTicket or osTicket Awesome?


Reply
Posts: 20
Topic starter
(@alexbuckland)
Member
Joined: 6 years ago

Hey Stevland,

Yes, Cloudflare does an awesome of caching (as well as security - I block countries who should not have access as well) taking lots of load of the origin server but I have found when upgrading OSTicket unless it is disabled and then reenabled afterwards you get really odd results and pages not loading or behaving properly.

The option is here:

 


Reply
Share: