4
I appreciate your feedback guys, I really do.
Quote:
Bender wrote:
What good does the core do me if it offers a restore i can´t run because the site is broken? 
Sure I guess but what good does a backup module do for you in the same situation? Plus with module creators coming and going and module projects either dying on the vine or being updated very slowly when new XOOPS versions come out, it seems unproductive to depend on the fluidity of some module creators good nature and free time.
Quote:
Dave_L wrote
I don't know if that feature is planned, but IMHO, it shouldn't be high priority.
Even if the feature were available, I wouldn't use it. I do my database backups either using phpMyAdmin or the mysqldump command (for a manual backup), or a cron script that uses mysqldump (for automatic backups).
phpMyAdmin is a reliable, actively maintained tool. It's applicable to any MySQL database, not just XOOPS. Why re-invent the wheel, especially when the core developers are already so overloaded with work that the development schedule is far behind?
I understand and I guess it goes to the question of who XOOPS is directed to. If the answer is geeks and developers (like me) then you're absolutely correct - hack your own backup. If XOOPS is aimed at everyone though, including simple website designers and enthusiasts who don't really know their way around MySQL and phpMyAdmin then I have to disagree. It seems to me XOOPS is designed to be easy to use, point and click, drag and drop (unless you want it to be more technical, because it can be). For those users who gravitate towards XOOPS for it's ease of use and relative simplicity, I submit they need an easy to use and relatively simple way to run backups.
At the very least I suppose there should be a document that spells out step-by-step what one must do to make a complete backup just in case something goes wrong.
"I'm going to see if this internet thing takes off" - someone told me this when I suggested he needed a website.
