nfong

Also saw this warning:

[18-May-2023 23:31:51 UTC] PHP Fatal error: filesize(): Cannot use output buffering in output buffering display handlers in /home/123/public_html/web/wp-content/plugins/webp-express/lib/classes/BiggerThanSource.php on line 23

Using plugin 1.4.0 and PHP 8.1.15 still get a lot of warnings

Bunch of warnings show up if you have debug enabled for wordpress:

Deprecated: Return type of FS_Key_Value_Storage::offsetExists($k) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/a2076/public_html/xxx/wp-content/plugins/wp-twilio-core/freemius/includes/managers/class-fs-key-value-storage.php on line 309

Deprecated: Return type of FS_Key_Value_Storage::offsetGet($k) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/a2076/public_html/xxx/wp-content/plugins/wp-twilio-core/freemius/includes/managers/class-fs-key-value-storage.php on line 317

Deprecated: Return type of FS_Key_Value_Storage::offsetSet($k, $v) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/a2076/public_html/xxx/wp-content/plugins/wp-twilio-core/freemius/includes/managers/class-fs-key-value-storage.php on line 301

Deprecated: Return type of FS_Key_Value_Storage::offsetUnset($k) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/a2076/public_html/xxx/wp-content/plugins/wp-twilio-core/freemius/includes/managers/class-fs-key-value-storage.php on line 313

Deprecated: Return type of FS_Key_Value_Storage::current() should either be compatible with Iterator::current(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/a2076/public_html/xxx/wp-content/plugins/wp-twilio-core/freemius/includes/managers/class-fs-key-value-storage.php on line 328

Deprecated: Return type of FS_Key_Value_Storage::next() should either be compatible with Iterator::next(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/a2076/public_html/xxx/wp-content/plugins/wp-twilio-core/freemius/includes/managers/class-fs-key-value-storage.php on line 339

Deprecated: Return type of FS_Key_Value_Storage::key() should either be compatible with Iterator::key(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/a2076/public_html/xxx/wp-content/plugins/wp-twilio-core/freemius/includes/managers/class-fs-key-value-storage.php on line 350

Deprecated: Return type of FS_Key_Value_Storage::valid() should either be compatible with Iterator::valid(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/a2076/public_html/xxx/wp-content/plugins/wp-twilio-core/freemius/includes/managers/class-fs-key-value-storage.php on line 362

Deprecated: Return type of FS_Key_Value_Storage::rewind() should either be compatible with Iterator::rewind(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/a2076/public_html/xxx/wp-content/plugins/wp-twilio-core/freemius/includes/managers/class-fs-key-value-storage.php on line 375

Deprecated: Return type of FS_Key_Value_Storage::count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/a2076/public_html/xxx/wp-content/plugins/wp-twilio-core/freemius/includes/managers/class-fs-key-value-storage.php on line 389

Deprecated: Optional parameter $message declared before required parameter $args is implicitly treated as a required parameter in /home/a2076/public_html/xxx/wp-content/plugins/wp-twilio-core/helpers.php on line 109

Mostafa,

I will check

• This reply was modified 2 years ago by nfong.

Deal pod – Category field is field type Relationship > Pod Categories

(Nothing set in the Related to field)

In your code, is that expecting it to return the category parent ID or something else?

Under 2.7.31 this returns the integer category number of the parent of this deals category.

Type Custom Taxonomy

Storage Type: Table

https://user-images.githubusercontent.com/5952458/217164112-ba98cf6d-d60e-44fe-936b-4b1e295f3ba2.PNG

https://user-images.githubusercontent.com/5952458/217164659-d639567b-75b7-4f43-aea2-d24d0392fd3f.PNG

This doesnt work in 2.8, but is ok in 2.7.31. Did syntax change?

$deal->field(‘category.parent’);

• This reply was modified 2 years, 1 month ago by nfong.
• This reply was modified 2 years, 1 month ago by nfong.

The message was Reassigned fields with invalid groups.

Screenshot uploaded to github issue.

I did this on a staging server, I haven’t repair the production server and can dump any data that may be of use to diagnose the 2.8 upgrade process.

• This reply was modified 2 years, 1 month ago by nfong.

Updating 2.7.31 to 2.9.11.1, Use Tools – Repair the messed up pod. The pod and its fields now shows up okay in Edit Pods.

Code we use to lookup a field in this pod – is returning 0. Need to investigate cause.

Not the problem. Double checked it and it is pure text.

This is in the SAME installation, not on a different one.

Create 2 pages, paste in the same code, one works, other just outputs the code.

Consider switching to the WordPress 5.5 and newer built in sitemap. Anytime I can get rid of a plugin is good!

Wordpress created Sitemap located at:
domainname/wp-sitemap.xml

If have another sitemap plugin running, it may prevent you from accessing that url.

This plugin gives you some control over it.
https://www.ads-software.com/plugins/wp-sitemaps-config/

• This reply was modified 2 years, 10 months ago by nfong.

Got details and it is ok:

WordPress will resolve partial URLs and redirect to the most likely location. This functionality is called Canonical Redirects.

This is part of the core WordPress software and is not considered to be a security vulnerability.

I scanned against my site and just replace the domain name for example purposes.

Folks can do their free trial and try it against their own websites.

wp_encode_emoji( string $content ) worked well.

https://developer.www.ads-software.com/reference/functions/wp_encode_emoji/

I had a similiar problem. The plugin used to work with wordpress pods, but with the current release of pods, it does not copy custom post types.

A fix would be great!