Re: Few Questions on phpBB Mod.
haselhurst wrote:
"NOTE: This means you can't enable guest posting to your forums. It won't hamper guests in any way other than disallowing them to post. phpBB recently improved security with their session IDs so this code strikes a perfect balance between session ID integrity and search engine spidering."
On my forum people who are not logged in can still post (this is how I set it in admin) so I don't understand above comment. This is trivial, I am just curious!?
They can still post if they accept cookies. Those who don't may have problems.
Quote:Does anyone know roughly what percent of people don't use cookies on internet?
I saw that you got some general info on that already, but do note that you are barking up the wrong tree.
How many users on the net who generally reject cookies is not the issue, but rather those who do not elect to set the cookie when logging in.
Netwide stats on browser settings won't reflect on this at all.
Quote:For example, if not logged in then top post in my forum has URL of;
forum/about45.html (link on left to page title)
and also;
forum/post-74.html (time / date link on right to last post)
Yet both these links go to same page (last post may take you to lower anchor heading on same page if there are several replies).
So I wonder why these are different URLs.
One is a link to the topic, the others are links to individual posts. It would make more sense to have those turn up as links to the topic with subsequent links to bookmarks on the page where the post is.
It sounds like an easy change until you note that pagination will have to be addressed.
Ultimately, it's easier to just robot.txt exclude the post urls.
Quote:However, if someone makes an external link from another website to this post, there is a fair chance they will login to page and copy URL, and thus link to a dynamic URL that Google does not spider. I assume that this is a wasted inbound link (and is confusing).
It's not wasted, but it does split up the IBLs. Not a huge deal but yes, not optimal.
Quote:Any thoughts on this, and in particular why the latest post URL is of the type;
post-x.html
and the actual post heading link is of the type;
aboutx.html (which i take to be the 'real' page!)
when they are the same page content.
aboutx = topic
post-x = post
Ultimately, I will make the static url mod work for logged in users as well, but I am waiting for phpbb 3.0.0 to do so as some urls may change.
Quote:
i) Do you see any problems with this (my link checker seems to show that it works in blocking these files)?
The robots.txt should really not have any wildcards etc. How to deal with them is outlined here:
http://www.able2know.com/forums/viewtopic.php?p=1134609#1134609
(BTW, that's a post url, and is a good example of why the post urls are useful)
Quote:iii) Why do you put $ at end, what does that do?
You should remove it. It's a regex symbol and some spiders were indicating that they would support wildcards and the like. But that never took off so you should use the methods I outline in the post I link to above.
Quote:iv) From my link checking I did not notice that your code made any difference to files accessed by spider / link checker. I assume that the * means one or more characters (or just one?). I read that the use of * is not standard robots.txt code, but that Google does read it OK. So I had to add;
Disallow: /forum/post-
to block those files as your;
Disallow: /forum/post-*.html$
did not seem to work for my link / spider checker.
I'm not sure whether even google supports the wildcard anymore. But you got the idea on how to deal with it.
Quote:5. Finally, I realise that I had to modify your mods to hard code title for my forum (in lang-main.php). Are there any other changes that I should have done to your mods that relate to making it site specific. And related to this, if I want to change default URL name from;
pagex.html
to my own name, e.g.
science-articlex.html
where do i do this?
You should do this in the files that are modified in the static url mod.
An easy way to do this would be to do a find/replace on strings (text bits) that you know are unique to the files.
Make sure that the changes are duplicated in both the php and .htaccess files and you are all set.