Welcome Guest. Please Login or Register  


You are here: Index > Softaculous Inc. > News and Announcements > Topic : Webuzo 2.7.0 Launched



Threaded Mode | Print  

 Webuzo 2.7.0 Launched (8 Replies, Read 16552 times)
webuzo_manager
Group: Webuzo Team
Post Group: Elite Member
Posts: 271
Status:
Hi,

The Webuzo Team has released Webuzo 2.7.0.
This version introduces a major new Feature and some improvements.

Features:

1) Remote Backup and Restore support added in Webuzo.

2) Added Quick Install option for scripts which will ask minimal install options and use the default values for the remaining options. This is added for a quick installation experience. Admin can set Quick Install option as the default install option from Softaculous Admin Panel -> Settings page.

3) Added option to backup installations to GoogleDrive. Google Drive backup location can be added from the add backup location page. Click here for guide.

4) Endusers can now select what to backup while upgrading an installation from Softaculous Enduser Panel i.e. Full Backup, Backup Files, Backup Database, etc.

Improvements:

5) Added support for Tomcat 8 configuration.

6) Space usage for all email accounts will be cached to reduce page load time.

7) Now you will be able to configure CRON Jobs on even-odd days.

8) Added a notice on the script install form for the scripts that are not updated for more than 2 years. This is to make sure that the user is aware before
installing the script that the script has not been updated for long time. Admins can disable the outdated scripts from Webuzo AdminPanel -> Software page.

9) Allowed to use . (dot) in the data directory name for scripts that need a non web accessible data directory. This will let users make the data directory a hidden directory.

10) When redirecting a user to the SitePad editor server it will check the language selected in Webuzo and by default that language will be selected in SitePad.

Bug Fixes:

11) Minor navigation fix for universal search bar.

12) Fixed an issue where Squirrel Mail login used to fail with the following error : "0: php_network_getaddresses: getaddrinfo failed: Name or service not known"

13) If PHP 7.2 was the only installed PHP then Apache Web Server was unable to run under suPHP and FastCGI. This is fixed now

14) Remote Import was not working for scripts that had data directory e.g. Moodle. This is fixed now.

15) The Related Scripts section on the script overview page did not load properly in Chrome and Opera. This is fixed now.

App Updates:

16) Added support for Ubuntu 16.04 LTS in MariaDB 10.0 and 10.1

17) We have added Python 3 with PiP and SSL support.

18) Updated Django to the latest version. Refer this Guide to create a starter project.

19) Updated ImageMagick to the latest version and added support for PNG delegate.

The upcoming version will bring more exciting UI Changes, features and changes.

Regards,
The Webuzo Team

Edited by webuzo_manager : April 26, 2018, 10:26 am
IP: --   

Webuzo 2.7.0 Launched
dmagoo
Group: Member
Post Group: Newbie
Posts: 4
Status:
Webuzo 2.7.0 bugs
Back-up files set to restore and uploaded to /var/webuzo/backup can not be seen by webuzo for restore unless created by that instance of the new version. You can create a new back-up, rename it and rename your uploaded backup to the name of the newly created file and will be able to restore with that method. Seems to be DB loging of the BU files so not going to help anyone restore a install that gets busted and re-deployed.
The default install now does not include everything needed by many apps for install (supporting library) for awstats etc. And some other bugs. Roundcube still default deploys with incorrect data in conf file after a proper setup/install.
None of which I would have found out if not for the bug in 2.6.9 where I had my webuzo update set NOT to auto update and it did anyway busting my install and forcing me to attempt a restore. If I'm going to spend this much time at a command line, I fail to see the benefit of the interface. If you do not know how to run a server, keep running webuzo and it won't be long, you will know how to do anything without it. :P
IP: --   

Webuzo 2.7.0 Launched
webuzo_manager
Group: Webuzo Team
Post Group: Elite Member
Posts: 271
Status:
Hi dmagoo,

>>Back-up files set to restore and uploaded to /var/webuzo/backup can not be seen by webuzo >>for restore unless created by that instance of the new version. You can create a new back-up, >>rename it and rename your uploaded backup to the name of the newly created file and will be >>able to restore with that method. Seems to be DB loging of the BU files so not going to help >>anyone restore a install that gets busted and re-deployed.

This is not a bug, from 2.7.0 we maintain a file  which includes the currently backed up files and Webuzo will only display the backups mentioned in the file.

During the upgrade process from 2.6.9 to 2.7.0 Webuzo automatically checked all the files in the /var/webuzo/backup directory and updated the file list.

It seems that you might have stored your backup elsewhere

2.7.1 will provide an interface to upload existing files :)

>>The default install now does not include everything needed by many apps for install (supporting library) for awstats etc.

Can you please let me know more about this?

>> And some other bugs. Roundcube still default deploys with incorrect data in conf file after a proper setup/install.

Since RoundCube is installed via Softaculous which can't provide a configuration which works for every server thus they provide a default config which you must modify before installing.

Webuzo provides Mail client settings on the Email account page for use in any Third party applications.

>>I had my webuzo update set NOT to auto update and it did anyway busting my install and forcing me to attempt a restore

Strange, let me check this with Dev team

>> If I'm going to spend this much time at a command line, I fail to see the benefit of the >>interface. If you do not know how to run a server, keep running webuzo and it won't be long, >>you will know how to do anything without it

We are sorry that you had to face these issues, we will take your opinion into consideration and improve our product even further.

Let me know if you are facing any other issues.

Edited by webuzo_manager : May 13, 2018, 1:19 am
IP: --   

Webuzo 2.7.0 Launched
dmagoo
Group: Member
Post Group: Newbie
Posts: 4
Status:
Well, be glad to update you on other things but until I can get everything up and running as it was at it's core, I do not yet know .

but you say>>>
This is not a bug, from 2.7.0 we maintain a list of file  which includes the currently backed up files and Webuzo will only display the backups mentioned in the file.

2.7.1 will provide an interface to upload existing files :)
?
Well, worse if it is not a bug, how would you expect someone who had backup files from 2.6.9 to restore them in fresh 2.7.0 ? (me) So now you need a backup of the backup files generated to be able to restore them ?
I took a lucky guess for what I observed and was able to bypass the issue. Most would not been able to do squat.
Just stop recording the files being backed-up and only displaying those that were, unless there is a format issue, you are removing the value of the backup in the first place.
So what is the value of backing up to other server if the system crashes and you loose track of files that were backed up with it.
If you can not rely on a backup file created the same day, how is there value in a backup system like that.
It is not like there is something fundamentally different about the format of the backup, and if there were a issue, I failed to find the proper documentation to point that out or the changes you speak of. You folks are deploying this stuff faster that you can properly test it. I don't like being a test subject. Slow down a little.
I have deployed webuzo over 20 times this year and never had it deploy the same way twice on the same OS/server config. That troubles me.
But I would really appreciate looking into auto updates running when the setup has been set otherwise . Apps are not auto-updating, it just appears to be the webuzo core. I think it also did this to me on 2.6.8 to 2.6.9 but I can't prove that. But the system crashed at deployment time. Same as 2.6.7 to 2.6.8 and is why I don't want it to happen till I am around/have time to deal with the consequences of the crash it generates.
I know not many are on centos 7 but I can't be the only one with these problems. At first I thought it was hacks but the log files do not support that. They each happen about 2 weeks past the deployment of new n.n.X version. So at this point, I don't waste my time looking for evidence of a hack.
But I do need the back-up restore system to function properly if this is to continue. or what's the point. More work putting it back together than building anew.

That all said, It's also not like I do not appreciate the hard work everyone does to make this better. But a little clean-up before adding new issues that break everything that makes it swell to work with might be in order. :)
IP: --   

Webuzo 2.7.0 Launched
webuzo_manager
Group: Webuzo Team
Post Group: Elite Member
Posts: 271
Status:
Hi dmagoo,

>>Well, worse if it is not a bug, how would you expect someone who had backup files from 2.6.9 to restore them in fresh 2.7.0 ? (me) So now you need a backup of the backup files generated to be able to restore them ?

Let me explain, If you have a backup from a previous 2.6.9 and you want to to upload it to a fresh 2.7.0, then just use the interface to upload the backup file and Webuzo will automatically generate the a list corresponding to the backup and it will be displayed in the interface from where you can restore it.

There is no need to upload any extra file.

So the situation that you have mentioned if a server crashes and all the files are lost then you can just upload the backup files again to the new server using the interface and the file list will be created again.

If you don't want to use the interface you can upload the file manually to the /var/webuzo/backup folder and run an update script which will reload the file list.

I am really sorry that this change caught you off-guard

We will try to document such changes better in the future to avoid any edge case for users.

Let me know if you have any further questions.

IP: --   

Webuzo 2.7.0 Launched
dmagoo
Group: Member
Post Group: Newbie
Posts: 4
Status:
Sorry to catch you off guard but, there is no 'interface to upload' that you speak of in my centos7 version 2.7.0 .
There use to be one in there a few versions ago. Manual uploading worked as of 2.6.9. Interface downloading is still there. Perhaps a missed bug in last version.

The option I used was the only available one to me, and 'spoofing' that to make it work. If you have a method, I'm all ears 'cause my mysql's are not restoring correctly either. Corrupted in some way that I can not log in even with newly generated passwords or the old ones. Even went back to earlier back-up that were known good from the last update crash.
I keep 2 months+ worth of DB back-ups off server.
A lot of good that does me if I can't upload and restore them 'and have them work'. Better off phpmyadmin manually backup the DB. And it looks like I should have been doing that over relying on the webuzo datadump backup.
I'm guessing you changed the 'format' of the DATA-DUMP-BACKUP without making any backwards compatibility considerations or those are just in major error.

Whatever the case, if you don't have a fix for this as-is, I'm going to have to remake all 11 of my personal webs that have taken me years to build-out.
But I don't think I want anything to do with your back-up again. But I would like to have my sites restored.
then....
I think rsync with cron for local and remote server mounted backups make more sense than this aggravation.
IP: --   

Webuzo 2.7.0 Launched
webuzo_manager
Group: Webuzo Team
Post Group: Elite Member
Posts: 271
Status:
Hi dmagoo,

We will be also providing a CLI script which you can execute after uploading the file to /var/webuzo/backup/ and the file will appear in the in the Webuzo backup page similar to what you expected in 2.6.9

There has been no change in the backup as well as the restore process, so sounds really strange that you have been facing issues on restore.

Also, the change of storing backup files in a file list was introduced in 2.7.0 so that remote backups made via the panel can be tracked.

It seems that the goal that you wish to achieve with Backup and restore is quite different from what it's intended to be.

Let me know if you have any more question or you can contact us via support ticket where you can let me know your issue in detail so that I can provide you steps that will suit your Workflow of backup and restore
IP: --   

Webuzo 2.7.0 Launched
dmagoo
Group: Member
Post Group: Newbie
Posts: 4
Status:
I think you missed the point.
'The upgrade' broke most of the install so I had to re-install FRESH and use the backup files from 2.6.9 that it could not see let alone read. I'm not doing remote backups, all local. You made the new without thinking of backward comparability at deployment. Not a issue if it deployed without error.

Left in the dark waiting for a fix... while my webs not functional.

How long can you go without your databases. Where is the fix  you keep talking about a month later?
IP: --   

Webuzo 2.7.0 Launched
webuzo_manager
Group: Webuzo Team
Post Group: Elite Member
Posts: 271
Status:
Hi dmagoo,

I don't think we have received any complaints from users complaining about broken installations.

About the database issue, can you please open a support ticket so that we can check this on your server as.
IP: --   

« Previous    Next »

Threaded Mode | Print  



Jump To :


Users viewing this topic
1 guests, 0 users.


All times are GMT. The time now is December 11, 2018, 8:08 am.

  Powered By AEF 1.0.8 © 2007-2008 Electron Inc.Queries: 11  |  Page Created In:0.303