sobrenome

Considering the new search system on IPS 4.7.1 that shows selected in the search bar the APP that the user is on, is it possible to always use Google search as default?

Is it working fine with the new IPS4 search feature?

Thanks! I have made the purchase on the community.

I want to renew the plugin, but in the new marketplace I see only “buy”, not “renew”.

Any news about read/write separation fix? ☺️

Anyone?

Removing the read/write separation the error goes away. Please patch this bug allow read/write separation. Thanks.

Running IPS 4.7.1, PHP 8.0.21 and MariaDB 10.6.8.

The only thing that I have changed is the database read and write separation. New error on logs: Error: Property access is not allowed yet (0) #0 /var/www/html/applications/core/modules/front/search/search.php(746): IPS\Content\Search\Mysql\_Query->search() #1 /var/www/html/applications/core/modules/front/search/search.php(126): IPS\core\modules\front\search\_search->_results() #2 /var/www/html/system/Dispatcher/Controller.php(118): IPS\core\modules\front\search\_search->manage() #3 /var/www/html/system/Dispatcher/Dispatcher.php(153): IPS\Dispatcher\_Controller->execute() #4 /var/www/html/index.php(13): IPS\_Dispatcher->run() #5 {main}

Same issue on self hosted. Error: Property access is not allowed yet (0) #0 /var/www/html/applications/core/widgets/stream.php(198): IPS\Content\Search\Mysql\_Query->search() #1 /var/www/html/applications/cms/sources/Blocks/Block.php(242): IPS\core\widgets\_stream->render() #2 /var/www/html/system/Theme/Theme.php(4620) : eval()'d code(136): IPS\cms\Blocks\_Block::display() #3 /var/www/html/applications/cms/sources/Pages/Page.php(1250): IPS\Theme\content_pages_52() #4 /var/www/html/applications/cms/sources/Pages/Page.php(2276): IPS\cms\Pages\_Page->getHtmlContent() #5 /var/www/html/applications/cms/modules/front/pages/page.php(116): IPS\cms\Pages\_Page->output() #6 /var/www/html/applications/cms/modules/front/pages/page.php(43): IPS\cms\modules\front\pages\_page->view() #7 /var/www/html/system/Dispatcher/Controller.php(118): IPS\cms\modules\front\pages\_page->manage() #8 /var/www/html/applications/cms/modules/front/pages/page.php(33): IPS\Dispatcher\_Controller->execute() #9 /var/www/html/system/Dispatcher/Dispatcher.php(153): IPS\cms\modules\front\pages\_page->execute() #10 /var/www/html/index.php(13): IPS\_Dispatcher->run() #11 {main}

I need to compare my custom global file with IPS global file.

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?