Integrated update module

eric redegeld Posted in Component Development 8 months ago

Platform Information:

OSSN Version: 8.1

Website URL (optional): —

PHP Version:

Error Log (if any): —

Browser:

Operating System: Windows / Linux / Android / iOS / macOS

Not a bug — a usability challenge.

Situation:
The current OSSN update module offers two options for updating components:

FTP upload

Remove and upload again

The issue with option 2 (remove/upload) is that custom files like language translations (e.g. ossn.nl.php) are deleted in the process.
Yes, you can manually back them up, but that means going back and forth between FTP or cPanel — quite error-prone and inconvenient.

Real Example:
Today, I updated the First Time Login Redirect component.
After activating the update, I received a 505 error.
Why? My custom .nl language file was missing and had to be recreated manually.

Suggestion:
Consider a more seamless update experience — like what HumHub’s Updater Module offers.
A built-in versioning system with preservation of custom files (or at least a warning/backup suggestion) would greatly improve usability and prevent downtime.

Replies
us David Orwig Replied 8 months ago

I couldn't agree more

Dutch Eric redegeld Replied 8 months ago

Okay fair and understandable answer.

Indonesian Arsalan Shah Replied 8 months ago

I am 100% agree with Micahel.

German Michael Zülsdorff Replied 8 months ago

Harry, you wrote:
"Consider a more seamless update experience" ...
I don't believe in anything like that. If you feel the need to change a component of mine for example, and some time later I decide to release an update for whatever reason: Which 'intelligent' updater would be able to decide if YOUR change is the more important, or MINE, or maybe BOTH should/could be merged?

And as for losing your own added or changed translations: There's the Custom Strings component
https://www.opensource-socialnetwork.org/component/view/1942/custom-strings
available to help you storing that kind of stuff in a safe place.

Dutch Eric redegeld Replied 8 months ago

well stupit to clean the log, but put back the old version, dit the same and now it works!!!
grrr beats me.
okay still i think an cool update module would be great

German Michael Zülsdorff Replied 8 months ago

Trying to reproduce your issue - having set my site to Dutch language

  1. installing FTL 1.3 -> no crash
    Image
  2. enabling FTL -> no crash
    Image
  3. proceeding to setup page -> no crash
    Image
  4. clicking save -> correct warning -> no crash
    Image

As we see, Ossn reacts as expected: Whenever a language string or completete language file is missing, it won't crash your site, but the coded key will be displayed instead.

Even more a 505 error points to something completely different. Thus, check your server's main error_log file because any error of type 500 and above should be logged there.