Forum Replies Created
-
In reply to: Open Links in new window
updated, see below
In reply to: Allowing New Users to pick their own passwordsDon’t send $500, that’s crazy. Well unless that’s a single day of your adsense or something, lol. Donate here.
https://bbpress.org/plugins/topic/instant-password/
Make sure you install the Human Test plugin with it.
In reply to: Allowing New Users to pick their own passwordsI now have this working as a plugin and will make it available later today. I expect donations from both of you considering the small fortunes you were willing to pay an outsider
In reply to: Allowing New Users to pick their own passwordsI suggested they change this in the core long ago and let the user choose passwords while sending only an activation link via email.
If you don’t need them to verify via a link in the email this could be written in an hour as a plugin. The code for password entry with re-entry verification can be lifted from the 1.0 alpha source.
I do recommend you use my Human Test plugin however.
In reply to: Topics Per Page plugin – new problemIt is possible whatever editor you were using was inserting some whitespace when you pasted the entire thing before one of the lines. What editor were you using?
ps. thank you very much for the donation!
In reply to: Topics Per Page plugin – new problemI have to leave for the rest of the day but essentially if you are able to add the rest of the rules without an error 500, then go back into
bb-config.php
and put back the line for slugs.Then the forum should start using slugs.
To finish up after it’s all working, go find those three extra rewriterule lines I posted much earlier and add those to the list and then you should be 100% done.
After those extra three lines are in, remember to test the front-page pagination which is what started this entire exercise in the first place, and hopefully they will be error free.
In reply to: Topics Per Page plugin – new problemI think we solved it then.
Try adding the rest of the rules.
RewriteRule ^topic/([^/]+)/page/([0-9]+)/?$ /Forum/topic.php?id=$1&page=$2 [L,QSA]
RewriteRule ^topic/([^/]+)/?$ /Forum/topic.php?id=$1 [L,QSA]
RewriteRule ^tags/([^/]+)/page/([0-9]+)/?$ /Forum/tags.php?tag=$1&page=$2 [L,QSA]
RewriteRule ^tags/([^/]+)/?$ /Forum/tags.php?tag=$1 [L,QSA]
RewriteRule ^tags/?$ /Forum/tags.php [L,QSA]
RewriteRule ^profile/([^/]+)/page/([0-9]+)/?$ /Forum/profile.php?id=$1&page=$2 [L,QSA]
RewriteRule ^profile/([^/]+)/([^/]+)/?$ /Forum/profile.php?id=$1&tab=$2 [L,QSA]
RewriteRule ^profile/([^/]+)/([^/]+)/page/([0-9]+)/?$ /Forum/profile.php?id=$1&tab=$2&page=$3 [L,QSA]
RewriteRule ^profile/([^/]+)/?$ /Forum/profile.php?id=$1 [L,QSA]
RewriteRule ^profile/?$ /Forum/profile.php [L,QSA]
RewriteRule ^view/([^/]+)/page/([0-9]+)/?$ /Forum/view.php?view=$1&page=$2 [L,QSA]
RewriteRule ^view/([^/]+)/?$ /Forum/view.php?view=$1 [L,QSA]
RewriteRule ^rss/?$ /Forum/rss.php [L,QSA]
RewriteRule ^rss/topics/?$ /Forum/rss.php?topics=1 [L,QSA]
RewriteRule ^rss/forum/([^/]+)/?$ /Forum/rss.php?forum=$1 [L,QSA]
RewriteRule ^rss/forum/([^/]+)/topics/?$ /Forum/rss.php?forum=$1&topics=1 [L,QSA]
RewriteRule ^rss/topic/([^/]+)/?$ /Forum/rss.php?topic=$1 [L,QSA]
RewriteRule ^rss/tags/([^/]+)/?$ /Forum/rss.php?tag=$1 [L,QSA]
RewriteRule ^rss/profile/([^/]+)/?$ /Forum/rss.php?profile=$1 [L,QSA]
RewriteRule ^rss/view/([^/]+)/?$ /Forum/rss.php?view=$1 [L,QSA]In reply to: Topics Per Page plugin – new problemOh I just thought of another possible problem.
Try also adding
Options +FollowSymLinks
after the
Options -MultiViews
That might be the entire 500 error issue.
Some servers require it for mod_rewrite to work properly.
In reply to: Topics Per Page plugin – new problemOkay now trying adding the first two forum lines the
/Forum/
.htaccessOptions -MultiViews
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /Forum/
RewriteRule ^forum/([^/]+)/page/([0-9]+)/?$ /Forum/forum.php?id=$1&page=$2 [L,QSA]
RewriteRule ^forum/([^/]+)/?$ /Forum/forum.php?id=$1 [L,QSA]
</IfModule>In reply to: Topics Per Page plugin – new problemAh okay. Well the “slugs” part will be the last part after the .htaccess is working to finally get slugs.
We should probably approach this in baby steps to see what triggers it.
That “Multiple Choices” error is not good.
It means MultiViews is still ON for some reason when it should not be. Maybe you did the MultiViews turn off incorrectly?
Right now I assume the webroot has a
.htaccess
withOptions -MultiViews
at the top, then the rest of what you listed above for WordPress. Like so:Options -MultiViews
RewriteEngine On
RewriteCond %{http_host} ^travel-writers-exchange.com
RewriteRule ^(.*) http://www.travel-writers-exchange.com/$1 [R=301,L]
# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_URI} !^/Forum/
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPressNow in
/Forums/
I want you to make a reduced .htaccess file like this:Options -MultiViews
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /Forum/
</IfModule>Make that minimal amount and see if it that still functions without a 500 error. (keep the slugs disabled for now)
In reply to: Topics Per Page plugin – new problemI doubt your host’s techs will help you with something so specific other than telling you to disable multiviews.
Apparently others here who use 1and1 solved it so you probably can too.
By the way, you are adding
$bb->mod_rewrite = "slugs";
to the bb-config.php correct?
In reply to: advertisements after the first messagedo something like this in your
topic.php
template just before<?php endforeach; ?>
<?php if (!isset($adsense)) { $adsense=1; ?>
<li>
adsense javascript goes here
</li>
<?php } ?>(untested)
Actually, I think you want to try disabling MultiViews
Options -MultiViews
Note the minus instead of the plus.
If that doesnt’ work, what happens when you try to go directly to
http://www.domain.com/forum/?new=1
when NOT logged in? 404 ?
In reply to: Topics Per Page plugin – new problemOh! I just realized your IP is on 1and1 (1&1).
There were reported problems with them.
I’ll have to research.
You can try also putting
Options -MultiViews
at the top of the .htaccess in the /Forum/ directory too. Note it goes above and before the first<if
(first line)In reply to: Topics Per Page plugin – new problemThere is a chance your host has multiviews already turned on by default so let’s make sure it gets turned off.
At the start of the root .htaccess try putting
Options -MultiViews
Other than that, I’m out of ideas for today and will have to “sleep on it”.
In reply to: Topics Per Page plugin – new problemBy the way, once we do get this working, you’ll need to add these three rules to the .htaccess in
/Forum/
because bbPress’s rule generator is not complete (and for my plugin to work)RewriteRule ^topic/?$ /Forum/ [R=302,L,QSA]
RewriteRule ^forum/?$ /Forum/ [R=302,L,QSA]
RewriteRule ^page/([0-9]+)/?$ /Forum/?page=$1 [L,QSA](put them just before
</IfModule>
)In reply to: Topics Per Page plugin – new problemTry replacing that new line as:
`RewriteCond %{REQUEST_URI} !^/Forum/
(note the entire line has changed)
In reply to: Topics Per Page plugin – new problem(removed)
In reply to: Topics Per Page plugin – new problemAh I forgot it’s wordpress integrated – that’s your whole problem with 500 error. I have to lookup the workaround.
In reply to: Topics Per Page plugin – new problemWell the logic is that her webroot works, it’s just the forums that 500 when the rewrite rules are present in the lower directory.. To me that’s a rule conflict that apache can’t resolve.
ps. all my post editing right now reminds me of another plugin I need to make – “look behind” when editing. Of course if ajax editing was put back in, we wouldn’t need that.
In reply to: Topics Per Page plugin – new problemWell it might validate but there still might be a conflict.
Has to be examined by hand.
In reply to: Topics Per Page plugin – new problemIt will indirectly fix the problem with page numbers.
Doesn’t actually fix the bbPress internal issue but avoids it instead. I still don’t understand why I can’t reproduce the error on my installs.
You are probably getting an internal server error because of a conflict with a rule in the root htaccess. Make sure you don’t still have the old rewrite rules in the root one. You can also post that root htaccess here for me to look at. Be sure to put it between code backticks.
In reply to: Topics Per Page plugin – new problemYou need to make sure the .htaccess is in /Forums/ and not the root of the entire site. Your host’s directory structure is a little strange but I don’t think it will interfere with mod_rewrite.
There is a possibility that there is a rule in the root .htaccess that is interfering the lower .htaccess. But let’s first make sure it’s in the correct directory.
By the way:
/Forum/topic/forum-guidelines-please-read
is correct.
/Forum/forum-guidelines-please-read/
is wrong.
bbPress needs to know that the string following is a topic, otherwise it doesn’t know what to do with it (it might be a forum).
/Forum/forum/forum-name
is also legit.In reply to: Topics Per Page plugin – new problemHmm that’s a really strange problem that I am going to have to explore a bit later.
You are using the final copy of the plugin correct?
And you didn’t modify it at all?
Even though I can’t reproduce the problem on my copies of bbPress, this may be an internal bug since I can workaround the issue by doing this (note the
?&
)http://www.travel-writers-exchange.com/Forum/?&page=2
ps. the best way to do pretty-permalinks is to use the .htaccess method with “rewrite” where you have to copy and paste the rules that bbPress offers here:
http://www.travel-writers-exchange.com/bb-admin/Forum/rewrite-rules.php
Once you do that, then you have to turn on the option in your bb-config.php
In reply to: Mass email functionAny shared host worth their salt will automatically, immediately and permanently suspend an account sending that many emails per hour anyway.
Any site sending that many messages needs a dedicated email server with an IP that’s registered on whitelists (costs $$$) so major providers will accept that kind of traffic. http://goodmail.com http://www.senderscorecertified.com http://www.isipp.com are examples of popular whitelist services. You also need to make sure the server has rDNS, SenderID, SPF and DomainKeys.
With some additional code and the use of cron, Detective’s code could be made to send only a few emails per minute, and track that the same domain does not get an email again within a few minutes. That might slow down the banning a little but we’re getting into spammer territory there and I’m not making such a tool available (also phplist does all that anyway).