1
animas
Backup Idea
  • 2005/4/27 15:21

  • animas

  • Quite a regular

  • Posts: 206

  • Since: 2005/1/30


We backup database.
What about core files?

Which files are modified during new XOOPS installation?

Or is there anyway core files might be modified unintentionally ?

2
Bender
Re: Backup Idea
  • 2005/4/27 18:28

  • Bender

  • Home away from home

  • Posts: 1899

  • Since: 2003/3/10


Core files are usually not modified except for mainfile.php.

Some modules do though (e.g. XOOPS IPB Module, Protector(i think) ...)

However you should notice that when installing them as usually you have to apply those changes yourself so you should be able to keep track if you modified files.

Most modules donĀ“t touch XOOPS core files. So in most instances you should not need to do constant backups. While a file backup from time to time could not hurt when you installed new stuff for example.

3
Mithrandir
Re: Backup Idea

Except for uploaded files and images. Unfortunately too many modules use folders within the module for images used in categories etc. so it's not just a matter of backing up mainfile.php and the uploads/ directory. It will get you far, though.

Forum posts, article texts and generally anything written is saved in the database.

4
animas
Re: Backup Idea
  • 2005/4/28 16:08

  • animas

  • Quite a regular

  • Posts: 206

  • Since: 2005/1/30


So backing up mainfile.php and Files(images, documents etc)is enough?
When a module is installed, is mainfile.php upgraded? Or it is just upgraded once when I installed xoops?

5
Mithrandir
Re: Backup Idea

mainfile.php only holds information about the database connection. Everything else (apart from the aforementioned images and other files uploaded through modules) is saved in the database.

Login

Who's Online

480 user(s) are online (150 user(s) are browsing Support Forums)


Members: 0


Guests: 480


more...

Donat-O-Meter

Stats
Goal: $100.00
Due Date: Nov 30
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $100.00
Make donations with PayPal!

Latest GitHub Commits