Search options (Page 4 of 6)

Here is a mod from weirdsilence using ip to country.
http://weirdsilence.net/131

Yes and no,

For the admin panel, it's ok : I have forgotten to upload the plugin folder (wasn't said to be done in the step by step readme so I didn't upload it)
I will try again with 1.2.8, but at first look I don't see what mistake I may have done (the panel works fine, saving my pref with no problem). What is wrong is not (to my mind) a php error : when I click on the doku.php, there is a problem and the browser doesn't recognize php but something else, that's why I'm invited to download. (With FF, I got a cryptic page - strange characters -UTF problem??)

Hi,

I have some trouble in installing pundoku with 1.2.7 ; I will try to explain what happens :

I believe I have followed every step as said in the readme and I failed.
When I tell the browser to navigate to http://localhost/forum/doku.php I get a cryptic page with Firefox (strange characters ; and what is strange is the fact I can't select them to copy-paste) and, if using IE, I get a message (2 windows) telling me (first pop_up window) that IE can't download the program (sic) and (second pop-up window) printing the well-known window of downloading in progress)

All the files are in the forum folder, or in forum subfolders ; none at the root of the site :

root
---/forum : doku.php, etc.
---------/ wiki
---------/ style / imports

etc.

I don't see where is the admin panel (I see nothing regarding the wiki in the punbb admin panel).

Installation done with 1.1 on punres
Will you help me ?

--edit--
In my idea the problem is that when I click on the doku.php link, the progam work as if it were a downloadable file : a pop-up (when using IE) asks me if I want to download, open, etc. the doku.php
Don't know what's wrong.

Thank you Connorhd,

I asked this question because I hope I will install this nice mod soon : so I would like to know wether I do upgrade to 1.2.6 or 1.2.7 ; if it doesn't work with 1.2.7, i will regret not having installed 1.2.6 instead of 1.2.7. (following me ?)
I'm also interested in some other mods working with 1.2.6 (don't know if they're ok with 1.2.7)...
Upgrading and installing is not very convenient for me (I do everything by hand, editing line after line in a notepad like, hey, not a hdiff guru).
Anyway, thank you.

Thanks for replying hcgtv

Done and working (clearing data from search tables, exporting light database ok, and rebuilding index).
abclf.

I agree : I think it is useless for search engine robots, but it may be useful for suggesting "same sort of topics/close subjects" to the user.
I wish you understand my english
gb.

Where did you find the code for the menu Rod ?
(où as-tu trouvé le code pour générer le menu ?)

gb.

1/ there is such a cokie
2/ the script identifies the cookie
3/ the script asks the database to see if the ban is effective at this time or if it has been suppressed, deleted...
4/ the ban is effective : banned / the ban is deleted : delete cookie
I'm not a programer

Thanks Rickard for replying,

In fact, what I would like is to avoid some posts being published without first approval.
I don't think censor words is an efficient way of censoring (who is using it? I may be wrong) (but it may be a cool feature for automating links for exemple) to keep forum cool when there are problems (flames?) though I think a pre-moderation for posts where some special words are included may be usefull.
It may work for rude words, spam, with good keywords.
I mean an automated feature should be nice (not sure, should be discussed, depending on the difficulty, and so on ; it is no more than a suggestion) : why not using the censor words script to pre-moderate some posts ? Or, in other words, why not improving the censor words tool : not replace words but pre-moderate (sort of report) post, especially against guest ?

Thanks,
abclf.

Sorry, I see I don't answer you
No, I don't want to block guests or anything like else

Hello Connorhd,

IP is not the "fatal weapon" neither
Of course one can delete cookie, but one can also change its ip, (or maybe use proxy, anonymizer) and so on.

What I understand in fact is that the protection is better against banned member :
When I ban a member, he will have to delete his cookie to come back, agree ? No way to avoid this step, ok ?
But, if i ban a guest, I'm limited to the IP/username/email : if he uses non static one, I will have to ban him day after day (each time his IP changes).
With the help of a cookie, he will need to delete this cookie first : it's a one more step. Yes, I agree, it is easy to do but it's annoying.

Thanks for your interest,
abclf.