NoGi

When I click on add review I get a blank page. I'll raise a ticket tonight when I get home as I can't see my php logs from here.

Love it, purchased

What change in IPS4 are you waiting for?

Great thanks, the Facebook issue is killing me atm with all the renames I have to do on threads.

Ooooh I just posted a request in custom projects just for something like this. I assume it will work standalone without needing classifieds app? I do my classifieds in the forum itself and wanted to be able to link feedback to a thread.

I'm guessing you ran into issues? Let me know if you want me to test for you.

Great stuff, can't wait.

Will try this later tonight, my current scores are pretty bad from GTmetrix with Page Speed E and yslow D.

I made the move to UTFMB4 while I was still on 3.4.7. I just had 4 or 5 columns left that were giving me issues which I've now resolved with @AutoItScript's help. At least it's all done now and I don't have to worry about it in future.

Like this one?

Actually, setting that to ignore seems to have worked.

OK, I think we may be talking about 2 different things. Even with the index gone I am still getting the error in ACP. Like I mentioned above, I've got the varchar already set to 191 but ACP keeps wanting to set it to 255 which is where it's failing.

Index gone:

ACP doesn't say to recreate, gives same error:

Confirmed through phpmyadmin:

In summary, I think I have it setup right at varchar(191) but, ACP and the upgrades fail on database check as IPS4 wants it to be varchar(255) which the utfmb4 collation won't allow me to do.

When I click on index down the bottom, it creates an index. A good chance I am still not doing this right though.

Yeah, my cms database key is the same. But what does it show for your blog_authorized_users column in blogs_blogs table? That's where one of my problems is. Mine is currently varchar(191) but the database check in ACP wants to make it varchar(255) and fails. I think this is where my upgrades are failing on database check as well.

My example is:

in mysql:

From auto repair

ALTER TABLE `blog_blogs` CHANGE COLUMN `blog_authorized_users` `blog_authorized_users` VARCHAR (255) CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci NULL COMMENT '';

Specified key was too long; max key length is 1000 bytes

I can't see any associated index?

The ones that are currently erroring for me via ACP are these:

here are some problems with your database. Normally it is safe to try to fix these problems automatically however if your community is large, you may want to run the necessary queries manually. If so, the queries to run are:

ALTER TABLE `gallery_albums` CHANGE COLUMN `album_name_seo` `album_name_seo` VARCHAR (255) CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci NULL COMMENT '';

ALTER TABLE `gallery_images` CHANGE COLUMN `image_parent_permission` `image_parent_permission` VARCHAR (255) CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci NULL COMMENT '';

ALTER TABLE `blog_blogs` CHANGE COLUMN `blog_authorized_users` `blog_authorized_users` VARCHAR (255) CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci NULL COMMENT '';

ALTER TABLE `cms_databases` CHANGE COLUMN `database_key` `database_key` VARCHAR (255) CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '' COMMENT '';

ALTER TABLE `nexus_licensekeys` CHANGE COLUMN `lkey_key` `lkey_key` VARCHAR (255) CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '' COMMENT '';

I've already converted them to MB4 with the smaller varchar length but it looks like this is trying to put it back to 255 which is why it's giving the error.

Hi @Mike John, how are you going with this?

I did mine a little while back now via phpmyadmin. Ran a similar query table by table and manually fixing up the index columns as they came up with the string too long error.

The other thing I did was to change the default collation for MySQL as well.

I went through this process prior to my IPS4 upgrade and it was a PITA. Had to change all the ones that were missed (due to default being UTF8 instead of UTF8MB4) manually. You'll run into problems with indexes using varchar(255) which in turn will cause problems when IPS release an update that has database changes.

Support have raised a bug for me so hopefully they will have a permanent fix for it soon but something to be aware off before you go changing the collation.

I've got 2 issues with the app at the moment on 4.0.6:

Password resets are causing the autowelcome message to be posted and users that register through Facebook SSO, it's not passing their username, instead I'm getting long strings like:

Hello 4e0bfefdbcdef52580f8aa9a6b76177f,

Welcome to my Forum.

Please feel free to browse around and get to know others. If you have any questions please don't hesitate to ask.

regards,
admin

It's this >one, an alternative to classifieds. If Trader Feedback works standalone it may still work out for me. Thanks.

Can this work with SalesPortal as well?