You are not logged in. Please login or register.
Active topics Unanswered topics
Search options (Page 7 of 354)
Smartys wrote:No, a domain name would have the same issue as the outside IP
Actually, a domain would solve the problem because then he could add the domain to his hosts file and point it to 127.0.0.1 
In my opinion, the real issue is why he can't access the site using the external IP from within the network. He must be using port forwarding in order for people to access the site externally, but for some reason, it's blocking him from accessing it from within the network.
Alright, based on this, we have decided to drop 4.0 support. In other words, if you intend to upgrade to PunBB 1.3, make sure your hosting company is running 4.1 or later. If they don't offer this support, switch to a different provider 
Because then the hook would be executed in the wrong scope.
5.1: 2.4%
5.0: 58.5%
4.1: 34.1%
4.0: 4.9%
Now, some of you have responded "x.x on all servers" or something along those lines which probably means the percentages for 5.0 and 4.1 should be a bit higher. Also, out of the two who have responded that your host uses 4.0, we know that at least one of them offers 5.0 if you ask for it.
Smartys wrote:Except that the default password handling was changed, which would lead to those "Client does not support authentication protocol requested by server; consider upgrading MySQL client." messages
Only if you build the mysql extension against the old 4.0 client libraries. I think most hosts build both the mysql and mysqli extensions against the latest client libraries which shouldn't lead to any problems.
Smartys wrote:Except when you tell a user that their code using mysql_* functions needs to start using MySQLi functions.
Yeah, but that's only if you need to use any of the added features. The mysql extension works with later version of MySQL as well.
As much as I appreciate your work, since PunBB 1.2 does not properly support UTF-8, I don't believe we will be adding these to the download page. PunBB 1.3 on the other hand, which is coming shortly, supports UTF-8 out of the box.
Jérémie wrote:Rickard wrote:Weird that they're running completely different MySQL versions on different servers
A lot are. Especially since MySQL changed its password() field handling (at 4.1, I think) and it was a support nightmare from what I hear.
That was only a problem if you had a different version of the client libraries. This isn't an issue for a hosting company because when they update MySQL, they just recompile PHP at the same time.
Hob Bramble wrote:midPhase - http://midphase.com
I probably ought to get on them about upgrading that...
Apparently, you can just ask and they'll move you to a server with MySQL 5. Weird that they're running completely different MySQL versions on different servers
Hob Bramble wrote:4.0.27-standard
Might I ask what host that is?
Based on the replies so far:
5.1: 3.6%
5.0: 60.7%
4.1: 32.1%
4.0: 3.6%
quaker: Might I ask what hosting company is providing you with 4.0.27?
On a related note, I just went to mysql.com and they don't even provide links for 4.0 downloads in their download archive anymore.
We're considering dropping support for MySQL 4.0 and older in PunBB 1.3. The reason we're considering this is that proper character set support was not added until 4.1. However, before we make any such decisions, we need to know what you guys think about it. Or rather, which version of MySQL you're using on your production server (web host, dedicated etc).
You can check your MySQL version by going to the admin interface start page and looking under "Database" at the bottom of the page. We would appreciate if you could just check your forums and copy/paste the version number in this topic.
Cheers,
Rickard
Edit: Please note that we're not particularly interested in which version you use for development
The reason the field is that large is because of a peculiar behavior in IE6 (not sure about 7). If you post non iso8859-1 content into a form where the content-type of the page is iso8859-1, IE6 will submit the characters as HTML entities (or rather numeric character references). This means PunBB receives the text as a stream of & #1234; (without the space) type entities instead of the actual character. In order to solve this in 1.2, I just decided to store the HTML entity directly in the database and therefore increased the size of the fields.
In 1.3, this will no longer be a problem.
eric235u wrote:as a side note, a friend of mine has mentioned that he just changes the user agent for his browser to googlebot and is able to read most content without registering.
I've always wondered whether hiding content from non-bots in that way is "allowed" by the search engines. In my opinion, it should be penalized. There's nothing more annoying than googling for something and then finding that the content isn't visible unless you register or spoof your user agent.
We're having some problems with the server. We're on it.
Having all of them in the same array actually makes more sense as compared to what we have now. Hmm.
We've discussed this and here's what I think we'll do. The localization of URL's is still a very rare phenomenon and we're not so sure it's something people would want. Instead, we'll provide a simple extension that loads any set of localized rules (if available).
Yeah, I don't know why, but it just needed to be reset.
The documentation there isn't complete. If your forum resides in a subdirectory (e.g. example.com/forum), you also need to make a few modifications to the .htaccess. We haven't quite figured out how to instruct users how to do this though.
Tell you what, I'll bring it up with the other guys on the dev team.
Yeah. The documentation is getting an overhaul for 1.3. For that purpose, a wiki might not be a bad idea.
Indeed. Happy New Year folks! Give us a few more days and we should have 1.3 beta up for grabs.
Although I like the idea of using the default language as a basis for which rewrite rules to use, there is another issue to consider. Extensions can modify and extend the rewrite scheme. However, if a forum was running a non-English rewrite scheme, any extension that tries to modify the rules is likely to fail.
Posts found: 151 to 175 of 8,829