Search options (Page 6 of 16)

lol, i thought i was the only one using that kind of primitive self documentation technique. It works pretty well.

I don't like the color scheme that much, but that's me.
Nice job, i love the way you placed the links over those spicky metal bands, perfect integration.

He might just ask paul

defenatly the manual. php.net
my choice

All database content migration is possible if you have the necessary data on it and dare to code migration tools.

You will need somewhere to define by hand the source and destination forums match.

Also, some user policies need to be defined, like, what to do with duplicated emails, nicknames, et all

and more stuff that i don't remember of

Is there any merge tool out there?

eheheh... I wonder if vanslyde  or any other person will actually trust me with any tips after this.
It's the mnemonic i have in my head... "update table set...where" sorry...

ok.. so... let's see if the 3rd is the final one:

UPDATE posts SET user_id=X WHERE id=Y;

The solution you pointed would work if you were migrating from another DB system than sqlite.

The problem is that SQLITE is typeless am mysql is not.
In a mysql database, every table column has a datatype while in a slite it does not.

This makes it impossible to create a tool that would convert a sqlite database into other 'type' of database. You need to know the database structure.

The procedure i described is not that difficult, if you maintain a forum that's a actually an opportunity to try out stuff and learn a bit.
Otherwise you will have to fix somebody to do that for you.

I have just reply to a similar question

Check out this topic:
http://punbb.org/forums/viewtopic.php?id=16512

It's the same, replace sqlite by postgresql.

It's not so difficult, but yes, it's a bit tricky due to sqlite being typeless. Punbb database schema is the exact same if you use sqlite or mysql, it couldn't be other way anyway.

So, this is what i suggest for unexperienced users:

1. Create a fresh installation of punbb with a mysql database.
2. Using a mysql management tool like pypmyadmin, sqlyog, whatever, generate a SQL file containing the 'create table' statements. Save that file.
3. using a sqlite management tool create a sql file with the insert statements and save it too.
4.create a new empty database on your mysqlserver.
5.Populate your database, use the first sql file to create the tables and the last one to insert the data on them.
6.delete the instalation and database created on point 1

sirena, do your have to set manually on google every url you put ads on? If not you should not fear this. I don't know if you understood how this works, but the pages are the exact same, only the url changes. The diference here is: you will get your google visitors on your same old pages but they will reach then through a different url, that's all.

I actually use this mode in another way, instead of poiting the rewriten urls to my viewtopic.php i point them to viewprintable.php, another mod out there. This way, the users that arrive from google will arrive to the topic printable page. If you do this you can put ads on those pages and keep your original topicview pages ads clean so you keep your regular users from seeing ads but you still show them to your google visitors. It depends on what you want to achieve.

glucarelli, there is no way extended characters are causing any trouble because they simply are token away. Including them in the urls is not recomended at all and can cause you a lot of trouble. If you still want to include them i would sugest you replace 'é' by 'e', 'ç' by 'c', etc. You can make this replacement in the fucntion clean_url() on my mod.

You can change the rewriting to the format you pointed, but you will have to go through the mod and change it yourself. You need to adapt the regex both in your the function clean_url() and in your .htaccess and you need to twaek the link output in lines:
107,88 and 141.

For those concerned about duplicated content here is what you have to put on your robots.txt

User-agent: *
Disallow: /viewforum.php
Disallow: /viewtopic.php
Disallow: /profile.php
Disallow: /userlist.php

Dont  forget to include the path.
I will give this a try for one month to see if it really maters in any way.

a bit too easy to break. If a user would hapen insert the previous value inserted in the banner he/she would quickly find that weakness, also we are talking about it in here where everybody can read us.

But, yes, a non visual captcha is in my opinion a beter idea then a visual one.

There is also a akismet module which works cool for me.