Stuart Silvester

10 hours ago, SUBRTX said:

is there an option to disable request pii data and account deletion? Thanks.

At this time, it's available to all members.

We've just pushed out a patch that should address these issues with appearing to be logged out on first visit.

Please apply it from AdminCP > System > Get Support  - In the 'Invision Community' box, you'll see an optional patch (if applicable to your community).

I would recommend trying 4.7.11, we did update an authorize endpoint to the v2 API instead of v1. It's possible that it may be related to this since the error response mentions the v1 API.

REST API v2 is the latest version, v3 does not exist.

It sounds like you may have a Javascript cache issue, go to AdminCP > Support > Clear Caches to see if that solves your problem.

2 minutes ago, Grant_B said:

I do now and the issue goes away.

With it enabled the fault occurs - it doesn’t think the user is logged in when starting a new session (browser closed / opened or session expired) - on the second visit of the new session it does log the user in so the cookies are working it’s just the first visit shows then logged out.

Perfect, thank you for the follow up. Do you use a CDN such as Cloudfront or Cloudflare(that will cache pages based on the cache-control headers)?

I've made some notes and will further test this.

1 hour ago, Wolfie said:

Now a 1054.

 

Have a look in the 'core_log' database table for this error (and the array_map one), I would like to see the backtrace / more log data.

I bet you're regretting not upgrading from 3.x sooner 🙂

Hi Grant,

Thanks for the updates. It looks like you have the Cookie Consent / Guest Terms bar completely disabled, is that correct?

That wouldn't be anything related to how the redirects work. They work after the conversion based on the URL.

The quotes are updated during (or immediately after) the conversion in the `fixPostData()` method.

Are you sure this is the right server? 4.7.11 does not have anything on line 1505 of init.php.

That error is definitely that you're using PHP 7 instead of 8.

13 minutes ago, Wayne B said:

So it works fine on php 7.4 on the old server - migrate it to the new one as 7.4 as well and the error is reported. All login details and database details are present and correct. 

I dont understand it.

Wayne

Right, but you have uploaded the files for 4.7.11, so now you must use PHP 8.0 or 8.1.

For some reason your server doesn't appear to be using PHP 8 when loading Invision Community, it would be worth talking to your web host about that. Additionally, it might be worth making sure that your domain name is loading content from your new server and not your old one.

Maybe your MySQL hostname is wrong, something isn't specified correct in the config. - https://www.google.com/search?q=mysql+"No+such+file+or+directory"

That's not really related to the other issue you are seeing though. You're definitely running an older version of PHP (when the framework loads) that isn't compatible. I would focus on figuring that out first.

It's not something we support at this time for various reasons ( in any of our converters ). I'm afraid we don't have any immediate plans to change this.

Your web host may be able to tell you, Invision Community doesn't overwrite this file.

7 minutes ago, Wayne B said:

mysqli PHP extension is installed. What else could be causing this error;

Fatal error: Uncaught mysqli_sql_exception: No such file or directory in /home/sites/3b/f/fd794f5001/public_html/board/upload/ips4_old.php:327 Stack trace: #0 /home/sites/3b/f/fd794f5001/public_html/board/upload/ips4_old.php(327): mysqli->__construct('localhost', 'polcom_aduser', Object(SensitiveParameterValue), 'polcom_livesite', NULL, NULL) #1 {main} thrown in /home/sites/3b/f/fd794f5001/public_html/board/upload/ips4_old.php on line 327

 

Well, it's two fold really.

The MySQLi exception is being thrown because whilst it's connecting to your MySQL server, it cannot use the database you're connecting to (check the details in conf_global.php are correct).

Newer versions of PHP throw an exception instead of an error here, I have just published an update to ips4.php to disable these exceptions.

2 hours ago, MMXII said:

Once the patch has been released, if I download 4.7.11 from the client area again, will the patch be included in the download package too?

Yes, anytime we release a patch it is included in new downloads.

Check your conf_global.php file, the `base_url` should contain https:// if it is http:// update it and then clear the caches via the AdminCP > Support page.

2 minutes ago, Wolfie said:

Now a new issue...

 

Use the latest release to upgrade [4.7.11], I assume you're using 4.7.10.

1 hour ago, Como said:

And what about quote headers? For migrated content, they appear to not link back to the origin post. Is that taken care of too once we have migrated to Cloud?

Quote headers will not link to the original content following a conversion, that isn't something our SMF Converter has support for.

1 hour ago, Como said:

And does this work for user IDs too. Because, I note, old user IDs do not match new, post migration.

Yes, User URLs will redirect.

This is a bug that we've fixed, we're preparing a patch for some common issues we're seeing in the PII/Cookie Consent feature. The patch will include this fix.

I did take a look at the code, nothing immediately stood out to me that could cause this. Please do let us know if you can reproduce it again.

Yes, the automatic redirects will take care of old style links for content. You just need to keep the converters application installed and enabled after the conversion.

It looks like this is due to the translated strings on the buttons being too long for the space available. We'll see what we can do although I do want to avoid the cookie banner overlaying the entire screen on mobile.

I cannot reproduce the issue with the forum selector (it uses the database to store the preference) it works perfectly fine for me with optional cookies disabled.

Optional cookies can be anything, it isn't possible or required to list them all. We only list essential cookies and what they do.