Wordpress plugin - changes per osTicket version

Key4ce

Hello,I been developing a plugin for wordpress for a while now with over 400 active installs it runs pretty well.https://wordpress.org/plugins/key4ce-osticket-bridge/however keeping up with osticket changes starting to become very difficult.on each subversion: osticket 1.9.3 , 1.9.4, 1.9.5, and now 1.9.7 basic database information has been relocated on each of them.as you can imagine that makes keeping up with the plugin incredibly difficult and also prevents us from adding new features to the list as we are constantly busy fixing up existing features that osTicket has changed.So i am hoping if there's a way where:1) osticket updates them self become less messy regarding the database changes, especially for simple subversions.2) maybe able to provide some information on basic database changes before release so we have enough time to adjust queries before new version comes out.3) if none of that is possible: maybe help keeping the plugin up2date for wordpress users?Regards,Marco

ntozier

There were no database changes between 1.9.5 to 1.9.6 to 1.9.7.You could always join the osTicket Avid users (Beta Testers) group.https://groups.google.com/a/osticket.com/forum/#!forum/beta-testers

Key4ce

Pretty sure there was atleast for Attachments (as 1.9.5.1 and 1.9.6 now works after our recent update, but 1.9.7 for example does not, already have reports for this). (we use the Attachment storage plugin to osticket to do the job).don't think beta testers will help much to detect query changes that should be implemented?the whole point is:the db changes so frequent that we litterally find it hard to keep the wordpress plugin up2date and functional.especially for subversions i did not expect the db locations, fields etc for existing features to change on nearly every update.it even started a debate amongst my devs to simply make a forked osticket included with our plugin to avoid going 1 step forward 2 steps back every couple of months.now obviousely i created a bridge for a reason and want to avoid that at all cost (hence this topic).

Chefkeks

I'm doubt you are correct regarding the database... My suggestion is that you download an really old version of osTicket (1.6 or 1.7) and then copy over the files of the latest version - you'll then see all database upgrades and the versions of osTicket which need a database upgrade.

Beside I personally think it would make much more sense to work on extending the API of osTicket, so you don't need to make sure with a lot of changes that new versions are still functional. Please note that I have not used the bridge yet not do I know how it technically works, but since we also had some special requirements and solved them via an external script instead of extending the API (because of missing knowledge since we are admins and not developers), but the advantage is that we can always update to the latest version mostly regardless of the changes.

There is already a pull request over at github to extend the API a little bit: https://github.com/osTicket/osTicket-1.8/pull/1753

Key4ce

You can actually check our plugin has a selection box for which osticket version your using.we now got: 1.9.3, 1.9.4, 1.9.5 and 1.9.5.1 =>next in line is 1.9.7each of them have differences in databases --> and each of them we had to recheck db's, adjust queries to fit that version.now we need to work on 1.9.7 again after finally having all issues out of 1.9.5.1 / 1.9.6 less then 2 weeks later 1.9.7 --> again need updates in DB. (strangely again the attachments that only just got changed in 1.9.5.1).Our plugin uses DB queries for the simple fact that people, both admins aswell as users generally want to read, and submit tickets within wordpress.where the original api atleast last i checked was just for submitting. (which atleast back then was very difficult to work with).All with all my main question is:why do db locations and method of storage of existing functionalities keep on changing.as that really makes it weird. i can understand that sometimes you want to increase efficiency etc.. but not by the extend and amount osticket is doing in 1.9.xit gets increasingly more strange as it seems this is mostly done unaware by the reply's it gotten so far...

ntozier

Q: don't think beta testers will help much to detect query changes that should be implemented?A: I'm not sure that your going to get any resolution to this conversation that you will like if you are unwilling to even try anyone's suggestions. Q: why do db locations and method of storage of existing functionalities keep on changing.A: They don't?People can specify where files are stored if they use the filesystem storage plugin. They were moved to the Database back in 1.7. That is still the default. There have been no DB structure changes for the last few versions. There was some changes in format of the data in the column for dynamic fields/forms as the feature continues to evolve, but it didn't necessitate a DB structure change.

Chefkeks

Ok looks like I now understand your problem with the database upgrade...

For my a database update is e.g. when a table is removed or added or a new column inserted and so on.

For you a database update seems to also include how the data is stored in the database since you need to read and update the data directly from the database.

Guess I understood it now, but honestly I guess you'll always need to modify the bridge to make it work in the future with new osTicket versions and sorry but as far as I know the developers want to keep the development speed at least with the focus on increasing instead of decreasing, so again, try to work with the API may and get in contact with the developers is still my best suggestion.

Key4ce

@[deleted] --> No resolution can come if you don't even accept osticket is modifying it.check our plugin, check what we had to change on each version change and i can promis you you will see exactly which locations has changed inside the db.Our plugin reads all settings incl storage path settings AND allowed extensions from osticket db thats not the issue.. the places where the info is stored within osticket db that keeps on changing is however.@[deleted]Yes exactly.tables moved.. colomns changed to new locations etc is what i was trying to explain :-)That it should change on each single subversion makes no sense however.i can speak from expirience that that is not normal.Ofcourse sometimes those colomns/ tables get re-arranged. but not on every single subversion.even 1.9.5 and 1.9.5.1 have changes in the db... it also makes little sense for most.The status difference i could still understand due to making it dynamic.. but the attachment changes in the past 3 versions for example makes no sense and has no added benefit in any way or case. (it's not the first time).I believe priority was another issue that had really no much sense in it.. and so forth.Meaning: It is something developers should prevent from doing especially on each minor update. the API obviousely doesn't suffice and will never provide true integration with other platforms so i don't think thats a right way to go unless the API is more dynamically developped (requesting specific data into specific places like a SQL query would do) .In the end our goal is to further integrate it with wordpress users, woo commerce products and so forth api's won't help there atleast not as it is at the moment.