Search options (Page 67 of 77)

Can't say as I've tried either of them, but they both work both ways I believe, extract and restore. Their documentation will tell you more.

What type of database? Mysql, Pgsql or Sqlite? What database management interface do you have available?

What did you alter before the problem occured?

[your-website-address]/[what-dir-you-installed-punbb-in]/install.php

For example:

http://example.com/punbb/install.php

Depends upon your config. 666 gives read/write access for all. First number is owner, second number is group, third number is everyone else. But, as I say, depends upon your setup what perms are needed. A 666 will be the easiest for testing, then change to minimal required perms once you've done the testing.

It may be specific to his installation. Just add that boxover line with the other script/link/style lines near the top of header.php.

One thing I have noticed is with certain ISP's who use the proxy/caching servers, whereby the users visible IP changes each time they view a different page, so you may have upto five apparent connections for one user, until they timeout. Just a thought.

Hell no. (I remember what happened last time I helped with truncation).

Looks like your script is gathering a following, Bingiman. Btw, apologies for not doing any updates on it over the last day or two. Got a tad sidetracked with another article/news cms I've been trying out.

I personally doubt it's anything that would become a core feature, (devs correct me if I'm wrong), but all the above should be fairly straight forward to add through a little, , coding. I would suggest your best philosophy for ease of design and resilience may be to have a root forum dir, with multi-forums then a second level directory within that forum_root, and the db lookups split between two db's, so that you have a global $pun_config['o_base_url'] which is referred from the master db, with separate user account and site information from a second db instance, (unless you want all user info in the same db, regardless of forum). There is a thread in programming regarding how to split the db queries over separate databases. Obviously, replacing relative paths with $pun_config['o_base_url'] would provide more resilience as well. I've done that with a lot of paths in the scripts which makes creating N depth directories plausible. (The redirects are the sneaky ones to find).

Just my personal opinion, of course. Another thing I found useful was adding an array for lang files, and calling them from common.php, to avoid any chance of forgetting to add a lang file require to a script if you adapted it.

Edit: Btw, best of luck if you decide to try coding this up. I'll be intrigued to see how this progresses.

You wouldn't need maintenance mode with links, either, as mv is atomic.

Just working upon your theory of './include'. What happens if a script needs to call one of your master scripts from a second level depth? i.e: root_forum_dir/scripts/script.php Your method would not work in that scenario.

Softlinks are cronable. No input required for those either. Horses for courses, really. Whichever is ones preferred method.