sobrenome

Same issue here on 4.7.1. Need to edit global.css to have the new search features displaying properly.

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?

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?

How to add the IAM data on AdminCP to allow OpenSearch to work with IPS Community? AWS does not allow open access anymore.

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.

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

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!

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?

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.

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?

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!