Jump to content
Mark
 Share


Get Ready For IPS 4.0!

IPS Community Suite 4.0, the most significant update to IP.Board and the rest of our apps we've ever made, is fast approaching a state where we'll be ready for a public preview and, soon after that, public beta testing!

We know most of you are just as excited as we are about this and can't wait to try it out.

With 4.0, we've made some significant leaps in terms of modernization, and it's possible that you might need to do some preparation before you're ready to install it. Notably, our minimum PHP and MySQL versions have gone up. It's the first time we've needed you to do this in 6 years, and the versions we need you to have have been around for a long time, we're not requiring the latest versions.

In addition, 4.0 is UTF-8 only (if you don't know what that is, it's a way text can be stored in your database which you may or may not be using at the moment) and while the 4.0 upgrade process will ask you to convert your database if you're not already using it, this is a moderately time-consuming process, so if you convert your database now, it's one less thing to worry about on upgrade day.


To make this process as easy as possible, we have created a little script which you can upload to your server to test if you're ready.

Download Now

 Share

Comments

Recommended Comments



I only ask because one of the sites I help out with has a host that won't raise this above 64MB for some reason (annoying, but things work fine unless installing a mega language pack), and wondering if I should be on the lookout for some other hosting for them?

 

Best thing to do: switch to a decent host.

Link to comment
Share on other sites

Stupid question (as usual with me, really), but is the memory limit required to be 128MB, or is that again just the advised limit, with anything lower causing issues entirely our fault?

 

 

I only ask because one of the sites I help out with has a host that won't raise this above 64MB for some reason (annoying, but things work fine unless installing a mega language pack), and wondering if I should be on the lookout for some other hosting for them?

 

It is recommended, and if you hit a memory limit error and are under 128MB, you would be referred to your host to reset the limit to the PHP default.

 

The script does not stop functioning based on this alone.

 

 

Given the proximity to beta, some additional blog entries on IP.Content 4.0 would be GREATLY appreciated!

 

They will be coming in due course.

 

 

Why no support with Suhosin PHP?

 

If you hit a problem caused by Suhosin, you will be referred to your host to resolve the issue.  As above with regards to the memory limit, the software does not stop functioning simply because suhosin is installed.

Link to comment
Share on other sites

Stupid question (as usual with me, really), but is the memory limit required to be 128MB, or is that again just the advised limit, with anything lower causing issues entirely our fault?

 

 

I only ask because one of the sites I help out with has a host that won't raise this above 64MB for some reason (annoying, but things work fine unless installing a mega language pack), and wondering if I should be on the lookout for some other hosting for them?

 

128M is actually the PHP default. There is no real reason it should be lower than that.

Link to comment
Share on other sites

 

Shall we expect initial release as Ip.Forum app only or will it include all the app's ?

 

Possibly. We want feedback and bug reports to be focused rather than letting everyone test everything at once. Since so much functionality is centralized now, opening up everything would lead to a ton of duplication. So it's possible we'll take things step by step, but exactly what that entails hasn't been finalized. For the beta, that would depend on how things go with the preview.

Link to comment
Share on other sites

The dom extension is enabled by default in PHP, but can be disabled, which is why the check is there. It handles some XML imports (languages and themes) and is also used for post parsing - using the dom extension allows post parsing to be more reliable, especially for BBCode parsing - no more preg_replace('/epic-regex/')   :tongue:

yes good news thanks! :happy:

Link to comment
Share on other sites

My server is running MYSQL 5.5.36 and PHP 5.4.29. Running the script, I appear to get errors all the way down the page. Anyone want to take a look here and offer suggestions as to what might be wrong?

Thanks!

Link to comment
Share on other sites

And is this big issue when I have this?

 

Some or all of the columns in your database are not using the utf8_unicode_ci collation (ibf_admin_login_logs.admin_ip_address is utf8_

slovak

_ci)

 

It's still utf8. Is really utf8_unicode_ci required?

Link to comment
Share on other sites

My server is running MYSQL 5.5.36 and PHP 5.4.29. Running the script, I appear to get errors all the way down the page. Anyone want to take a look here and offer suggestions as to what might be wrong?

Thanks!

You've given it an .html extension

 

And is this big issue when I have this?

 

 

It's still utf8. Is really utf8_unicode_ci required?

Yes.

Link to comment
Share on other sites

The converter is going unbelievably slow on my CentOS box.

 

IP.Board 3.4.6

MySQL 5.5

PHP 5.4.29

 

It's been running for 6 hours. For a forum with only 150,676 and 8,000 members, I'm positive this is a problem.

 

If you have a large board it may be worth checking out my converter for doing this.  I should note that it's completely unofficial but has positive reviews from those who have tried it and can leverage parallel processing on your linux server to speed things up.

 

http://community.invisionpower.com/files/file/6758-unofficial-multi-threaded-utf-8-converter/

Link to comment
Share on other sites

For clarification on the versions required, you do not need mysql 5.6 and php 5.4, these are recommendations only, the software will run just fine on mysql 5.1, and 5.5 as well as php 5.3.

 

Most hosting providers do not support mysql 5.6 at this time, so there is no need to worry, it works fine on 5.1 and 5.5. as well as php 5.3.

Link to comment
Share on other sites

mysql loses connection to my forum db when i changed to this

$INFO['sql_charset'] = 'UTF8';

and I dd change the prefix sl_tbl_line to

$INFO['sql_tbl_prefix'] = 'x_utf_';

 

this after converting all my tables to utf8

Link to comment
Share on other sites

 

If you have a large board it may be worth checking out my converter for doing this.  I should note that it's completely unofficial but has positive reviews from those who have tried it and can leverage parallel processing on your linux server to speed things up.

 

http://community.invisionpower.com/files/file/6758-unofficial-multi-threaded-utf-8-converter/

 

Thanks, but my server has no PCNTL functions.

 

Surely it can't take 10+ hours to convert a 100,000 post database.

Link to comment
Share on other sites

mysql loses connection to my forum db when i changed to this

$INFO['sql_charset'] = 'UTF8';

and I dd change the prefix sl_tbl_line to

$INFO['sql_tbl_prefix'] = 'x_utf_';

 

this after converting all my tables to utf8

 

Same issue here, sent a support ticket in and it got escalated. :s

Link to comment
Share on other sites




Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Add a comment...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...