Search options (Page 5 of 5)

Well, it's certainly fancier. Not sure I like it better, though. I'll have to get used to it
The problem is that modding only works if there are few changes. If this was a new release, I'd be going through hell to implement it.

BTW, I'm curious about the exit(); lines that you've been adding after the header(Location:...); I thought the parser would never execute code after that, but now I am not so sure it might be the client that upon receipt changes the request. I miss the Server.Transfer and Response.Redirect commands... sniff

Marc

Just for the record, I'd do it adding a cat id to the field:
1:link1
1:link2
1:link3
2:link1
2:link2
2:link3
3:link1
3:link2
3:link3
And filter the characters before the ; (or # or whatever).

Or simply use an array, what's wrong with that? Query the DB once, and order the records by cathegory. Then fill your array with one index equaling that of the cathegory.

If I understood the question, both are easy to implement.

Cheers,
Marc

Hmmm why not keeping a small db where you keep the name and revision in a sepparate field. add records after generatio or upload, that's pretty easy to do.

To read the latest revision filenames, it'll be something like
select name_field, max(revision_field) as revision_field from document_database group by name_field
(or avoid max and group by, if you want them all), you then compose the real filename as name_field."_rev-".revision_field

As an addition, you could serve the files directly to the requester, avoiding the need to give a direct link to the real file. If you need details, ask.

Now, my VAT number is...

Rickard, that is an unfortunate not well implemented feature of CSS, it should work with position: fixed, but I still have to see that work somewhere.

If you find out how, please let me know, I am also strongly interested in that. Never managed to do it solely with css, but would certainly be neater.

fixed 
The box's position is calculated according to the 'absolute' model, but in addition, the box is fixed with respect to some reference. In the case of continuous media, the box is fixed with respect to the viewport (and doesn't move when scrolled). In the case of paged media, the box is fixed with respect to the page, even if that page is seen through a viewport (in the case of a print-preview, for example). Authors may wish to specify 'fixed' in a media-dependent way. For instance, an author may want a box to remain at the top of the viewport on the screen, but not at the top of each printed page. The two specifications may be separated by using an @media rule, as in: 
Example(s):


   
@media screen { 
  H1#first { position: fixed } 
}
@media print { 
  H1#first { position: static }
}

Well, that's fine, modifying the mod is not that hard, however, there's always the problem of adding users to groups... well, maybe that's professional deformation, in my case, all users belong to one group or another, that is, there's one section exclusive for every type of user. So for me to assign the users to groups was easy, I did everything directly through SQL, I'd have to build a front end for that, and for group creation and modification (something else I did lazily ;-).

My other problem, is that I've been going through some security enforcement modifications, mostly encrypting cookies and hiding menus. I've also scrapped the copyright and link from the guest front page, cause I don't want non-users to be able to even see what software is running (that surgical removal was not that easy, since you have to dig deep into the code to find a place where it won't disrupt everything else... it would have been much easier to completely remove the copyright lines, but I've got this thing about giving proper credit...). The point is, I can find the easy lines to be mod, but maybe some subtlety will be lost, so... at this very moment, I can't release this mod. Give me at least a week or so, and maybe I will have something to show up :-)

Marc

BTW, an email server per se, is not possible through php. You can however create a cgi script or something alike as your own email engine, but php has the sendmail function that allows you to send email provided the machine is running an smtp engine.
There are packages, though, and they need not be large files, some viruses incorporate their own smtp engine (on windows machines that allow raw sockets, AFAIK).

But there are indeed email frontends that allow you to check your email from an imap/pop server and to send emails. No need to reinvent the wheel

Marc

Hehehe, next thing I'll search on google will be "open source webmail php mysql" ;-)

Marc

@Redhook: php is pretty simple to understand, most books deal halfway with the installation process, and most also deal with MySQL installation, which is not that bad if you don't have any experience at all with them.

Most important places are www.php.net (look for the manual) and www.mysql.net (idem), cause when you've got a doubt you'll go there to see.

Ok, the book I learnt from was from sitepoint, something like 'build your own website applications using mysql and php'. But I don't think it's incredibly better than anything else you'll find around. Hell, if you look around, you'll even find some free books floating around. Take whatever you're comfortable with. And then play a lot with it.
Since you already have a project in mind, that helps.

Marc

@Frank: Hmmm what you say makes lots of sense. I just didn't think it through this way, maybe cause when I set up the changes, I leave the "old" code commented out, and this way I can reverse a mod (cough, cough) easily, or at least I can reverse it

@Louis: sounds like a CVS repository to me...

Marc

Hehe, you knew it would solve it ;-)

Thanks!

Marc
Addendum: now you can re-release it with v1.1.1, just like the very version of punBB that is suposed to work with