sobrenome

IPS 4.6.8 added AggregateRating Schema to record pages. I have been using my custom schema on templates, like this one: {{\IPS\Output::i()->jsonLd['article']['about'] = array('@type' => 'PhysicalActivity', 'category' => 'StrengthTraining', 'image' => array('@type' => 'ImageObject', 'url' => (string) \IPS\File::get('cms_Records', $record->field_107)->url, 'height' => '800', 'width' => '1200'));}} Will the update impact on my Pages templates?

Nice! And we still does not have moderation to wiki databases….

Nice! This could come with the new Gallery app!

If we use Cloudflare that already uses IndexNow, how would behave an IPS IndexNow under layed?

Nice! Just added it!

Hello @Andy Millne! I don't know if I am wrong, but I have realized that when review is on for Pages database, there is no $record->rating_hits, only $record->record_reviews as long as the rating stars will be based on the reviews, so the rating hits are the same as the record reviews. Is that right? So I have used record reviews for ratingCount and reviewCount. {{\IPS\Output::i()->jsonLd['article'] = array('@context' => 'http://schema.org/', '@type' => 'Product', 'name' => $record->_title, 'image' => 'https://cdn.mydomain.com/ ' . $record->record_image, 'brand' => array('@type' => 'Thing', 'name' => $marca['nome']), 'aggregateRating' => array('@type' => 'AggregateRating', 'ratingValue' => $englishrating, 'ratingCount' => $record->record_reviews, 'reviewCount' => $record->record_reviews), 'offers' => array('@type' => 'AggregateOffer', 'lowPrice' => $lowPrice, 'highPrice' => $highPrice, 'offerCount' => $results_number, 'priceCurrency' => 'BRL', 'availability' => $availability));}}

@bfarber could help? @Jim M?

How to get the number o ratings and the number of reviews on Pages? $record->numberOfRatings() or $record->rating_hits are not working.

Running 10.5 with no issues so far. Waiting for 10.6 support on RDS.

Have you jumped already?

I am also interested in this upgrade from 10.4 to 10.5. Waiting for replies.

Thanks for the update @stoo2000! I have installed it a couple of minutes ago and so far so good.

I had the same issue. It locks the core_mail_error_logs table in an infinite loop.

And the error is not on php 8 only. It occurs on php 7, but php 8 is less tolerant to errors as I read. When I used Mail Bouncer on IPS 4.6 and php 7, my community was very slow for logged users. Here was the report.

Yes, I have noticed! Seems to be faster for logged users. Now is fast for all users, not only for guests! Excellent!

AWS Elastic Search is now going to offer Open Search: https://aws.amazon.com/pt/blogs/aws/amazon-elasticsearch-service-is-now-amazon-opensearch-service-and-supports-opensearch-10/

I lost access to AdminCP and had to open a ticket. IPS support helped me to use the recover mode and told me to disable Mail Bouncer. I would appreciate a new version fixing the bug. Thanks!

Hello, I have updated to php 8 and I am getting this error: [Wed Sep 08 11:03:20.893872 2021] [proxy_fcgi:error] [pid 1651:tid 281472812437904] [client 10.0.1.102:53118] AH01071: Got error 'PHP message: PHP Fatal error: Declaration of IPS\\bouncer_hook_Email::send($to, $cc = [], $bcc = [], $fromEmail = null, $fromName = null, $additionalHeaders = [], $autoSubmitted = true) must be compatible with IPS\\_Email::send($to, $cc = [], $bcc = [], $fromEmail = null, $fromName = null, $additionalHeaders = [], $autoSubmitted = true, $updateAds = true) in /var/www/html/init.php(902) : eval()'d code on line 83', referer: https://mydomian.com/admin/?app=core&module=system&controller=login&error=&ref=

Thanks @stoo2000!

The issue is coming back. It would be nice to be certain it MAIL BOUNCER is causing the issue or not.

My community suffered some MySQL server lock timeout caused by these queries: /*ips4::user::IPS\_Email::send:117*/ UPDATE `core_mail_error_logs` core_mail_error_logs SET `mlog_notification_sent`=1 It had 9268 TRX_ROWS_LOCKED. My community was very slow for logged users. Slow to post and slow to browse. I have disabled MAIL BOUNCER and enabled it again. The issue was gone. It would be nice to take a look at it. Thanks.