sobrenome

Same issue here on 4.7.1.

Need to edit global.css to have the new search features displaying properly.

9 hours ago, Marc Stridgen said:

I have moved this to our developer area for you, as this is custom development rather than standard support. 

Thanks Marc. Is it on Home > Forums > Developers > Customization Resources > Development Assistance? Could not find there.

Does anyone know in which php file ips4_IPSSessionFront is set for guests?

Please update to 4.7!

😊

By the way, using OpenSearch 1.3 without issues.

I want to serve cached pages for guests directly from Cloudfront cache (first hit). No origin request.

On pages requests IPS sends these headers (using Redis as cache method and 1 hour caching for guests on AdminCP😞

cache-control: no-cache="Set-Cookie", max-age=3600, public, s-maxage=3600, stale-while-revalidate, stale-if-error
set-cookie: ips4_IPSSessionFront=75kv76vm8so67kh861iqhu7jky; path=/; secure; HttpOnly

To cache pages on Cloudfront, these headers should not be sent: no-cache="Set-Cookie" and set-cookie: ips4_IPSSessionFront=75kv76vm8so67kh861iqhu7jky; path=/; secure; HttpOnly.

I don't care about users online counter and don't use any guest posting feature. Guests can only read content. There is no interaction for guests. For them, serving "static pages" from the CDN is fine for some minutes, what would be much more faster and less resource intensive.

Is there a constants.php setting to remove the set-cookie (IPSSessionFront) for guests?

On 7/27/2022 at 12:11 AM, sobrenome said:

How to add the IAM data on AdminCP to allow OpenSearch to work with IPS Community? 

AWS does not allow open access anymore.

If anyone is struggling with this, I have found on init.php ELASTICSEARCH_USER and ELASTICSEARCH_PASSWORD constants. So you can launch AWS OpenSearch with fine-grained access control (main user and password).

Running MariaDB 10.6.8 without issues.

I want to serve cached pages for guests directly from Cloudfront cache. No origin request.

On pages requests IPS sends these headers (using Redis as cache method and 1 hour caching for guests on AdminCP):

cache-control: no-cache="Set-Cookie", max-age=3600, public, s-maxage=3600, stale-while-revalidate, stale-if-error
set-cookie: IPSSessionFront=75kv76vm8so67kh861iqhu7jky; path=/; secure; HttpOnly

To cache pages on Cloudfront, these headers should not be sent: no-cache="Set-Cookie" and set-cookie: IPSSessionFront=75kv76vm8so67kh861iqhu7jky; path=/; secure; HttpOnly.

I don't care about users online counter and don't use any guest posting feature. Guests can only read content. There is no interaction for guests. For them, serving "static pages" from the CDN is fine for some minutes, what would be much more faster and less resource intensive.

Is there a constants.php setting to remove the set-cookie (IPSSessionFront) for guests?

On 7/18/2022 at 8:43 AM, Stuart Silvester said:

I believe we're using 1.2, which is the latest version AWS OpenSearch Service supports.

How to add the IAM data on AdminCP to allow OpenSearch to work with IPS Community? 

AWS does not allow open access anymore.

1 minute ago, Randy Calvert said:

If you're self-hosted, rather than do Cloudfront, I would suggest looking at Cloudflare.  You'll find it a MUCH MUCH easier integration.  Otherwise you're going to have to do a BUNCH of work, including potentially needing to setup SSL certificates, defending S3 buckets, configuring what content should be stored on S3, etc.  That's even before you get to the Cloudfront setup and figuring out your CORS settings and how long each type of content should be cached for.  

I am moving from Cloudflare to Cloudfront. Now Cloudfront has an always free tier. I am already using AWS EC2, S3, RDS, EFS, Elastic Cache and Open Search.

2 hours ago, Randy Calvert said:

There are a LOT of settings that would depend on your site.  Why don't we start with what don't you understand about it?  

It's an IPS website community. I still did not take time to check every setting. I looked for something here before.

5 hours ago, The Dark Wizard said:

Would it not be setup like any other CDN?

There are many fields to set on AWS Cloudfront.

Would be nice if someone using Cloudfront and IPS self hosted could share the settings.

Anyone using Cloudfront and IPS?

I will miss the SQL tool box. It is a downgrade unfortunately. I hope IPS reconsider this move backwards.

I have set compatibility mode on. Now it's running!

I guess that last time the access policy to the domain was the issue, even if security group and VPC access were ok. 

Thanks!

1 hour ago, Stuart Silvester said:

That error message suggests that Invision Community is unable to connect to your Elastic/OpenSearch instance. I would recommend checking that your web server has permission to access the instance and that it is online.

OpenSearch is based on Elasticsearch 7.10.2, not 7.1

Thanks! Yes, you are right! 7.10! Sorry about that. I will set up a new instance and update here.

Should I have to turn on "compatibility mode" to communicate the instance as Elasticsearch 7.10?

On 11/30/2021 at 3:13 PM, Stuart Silvester said:

Yes, that's right. You should see a bulletin in your AdminCP detailing the change and the new minimum requirement of 7.2.0.

Unfortunately it's not working. I have set a new OpenSearch 1.0 instance with the same settings of my old Elastic Search 6.7 and I get this error:

The server did not return the expected response. Check Elasticsearch is properly installed and accessible from your web server. If you visit the provided URL in your browser you should see details about the installed version.

Notice that OpenSearch 1.0 is the latest version and is based on ElasticSearch 7.1.

Very nice suggestion!

We need audio and video to go along to text communication.

On 11/19/2021 at 6:31 AM, Matt said:

Worth nothing, that if we offer an ES service ourselves, it'll likely be Opensearch we use.

So after the upgrade of IPS to 4.6.9 I will have to upgrade my AWS Elastic Search 6.8 to the latest version os AWS Open Search, right?

On 10/28/2021 at 11:36 AM, Matt said:

Yes we do monitor web core vitals and have plans to improve performance. 

Please give it priority! Thanks!

Yes, please!

It is not a support demand, it is just to know how the new Pages feature will behave before upgrading. The manuals were already upgraded to explain the new Pages feature? Thanks.

Thanks! I will check it!