Fatal error: Unsupported operand types with v2.7.12

Issue Overview

When saving custom post type:

Fatal error: Unsupported operand types in ..... /wp-content/plugins/pods/classes/fields/number.php on line 171

Expected Behavior

Current Behavior

My client updated to WP 5 at the beginning of December (currently on 5.0.3.) I see that our Pods automatically updated on December 12 to 2.7.12.

On January 5 he noticed this error for the first time – he doesn't think he made any entries or edits after between WP update and then. When saving custom post type "trail", we get:

Fatal error: Unsupported operand types in /home1/bookkeeper/public_html/OntarioNatureTrails.com/wp-content/plugins/pods/classes/fields/number.php on line 171

I also encounter the same error on front end when using WP's standard search if I enter the keyword "trail" in the search field – for other words, search works normally.

PHP 5.4.45

Happy to set you up as admin if that helps.

http://ontarionaturetrails.com

Thanks very much!

Vic

Steps to Reproduce (for bugs)

Hit "publish" or "update" when saving custom post type: trail
Enter the single word "trail" in WordPress search field

Possible Solution

WordPress Environment

5.0.3

Debug Information WordPress Version: 5.0.3 PHP Version: 5.4.45 MySQL Version: 5.6.41 Server Software: Apache Your User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:60.0) Gecko/20100101 Firefox/60.0 Session Save Path: /tmp Session Save Path Exists: Yes Session Save Path Writeable: Yes Session Max Lifetime: 1440 Opcode Cache: • Apc: No • Memcached: No • OPcache: No • Redis: No Object Cache: • APC: No • APCu: No • Memcache: No • Memcached: No • Redis: No WPDB Prefix: wp_ WP Multisite Mode: No WP Memory Limit: 256M Current Memory Usage: 90.852M Current Memory Usage (real): 92.500M Pods Network-Wide Activated: No Pods Install Location: /home1/bookkeeper/public_html/OntarioNatureTrails.com/wp-content/plugins/pods/ Pods Tableless Mode Activated: No Pods Light Mode Activated: No Currently Active Theme: OntarioNatureTrails Currently Active Plugins: • Akismet Anti-Spam: 4.1 • Broken Link Checker: 1.11.5 • Comment Images Reloaded: 2.2.1 • Contact Form 7: 5.1.1 • Elegant Themes Updater: 1.2 • Google Maps v3 Shortcode multiple Markers: 1.0 • Jetpack by WordPress.com: 6.8.1 • Ontario Trails Posts: • Pods - Custom Content Types and Fields: 2.7.12 • Regenerate Thumbnails: 3.1.0 • SAM Pro (Free Edition): 2.5.0 • Trail Pins: 0.1 BETA • Ultimate WP Query Search Filter: 1.0.10 • VaultPress: 1.9.7 • Widget Logic: 5.9.0 • WooCommerce: 3.5.3 • Yoast SEO: 9.2.1

Pods Package Export (helpful!)

{@post_title} characteristics<\/h2>\r\nLength:<\/b> {@length} \r\nDifficulty:<\/b> {@difficulty} (<a href=\"http:\/\/ontarionaturetrails.com\/trail-classifications\/\" target=\"_blank\">Trail classifications<\/a>) \r\nTrail surface:<\/b> {@trail_surface} \r\nTrail use:<\/b> {@trail_use} \r\n[if wheelchair_accessible]Wheelchair accessible<\/b> [\/if]\r\n[if wheelchair_accessible_partial]Partially wheelchair accessible<\/b> [\/if]\r\n[if accessibility-notes]Accessibility Notes:<\/b> {@accessibility-notes} [\/if]\r\n[if fees]Fees: <\/b> {@fees} [\/if] \r\n[if flora_fauna]Flora & Fauna:<\/b> {@flora_fauna} [\/if]\r\n[if amenities_attractions]Amenities:<\/b> {@amenities_attractions} [\/if]\r\n[if attractions]Attractions:<\/b> {@attractions} [\/if]\r\nContact:<\/b> \r\n[if website1]<a href=\"{@website1}\" target=\"_blank\">{@website1}<\/a> [\/if]\r\n[if website2]<a href=\"{@website2}\" target=\"_blank\">{@website2}<\/a> [\/if]\r\n[if contact_email]<a href=\"mailto:{@contact_email}\">{@contact_email}<\/a> [\/if]\r\n[if additional_contact]{@additional_contact} [\/if] \r\n[if trail_location]Find it:<\/b> {@trail_location} [\/if]\r\n[if gps-lat]GPS Coordinates (main trailhead):<\/b> \r\nLatitude: {@gps-lat} \r\nLongitude: -{@gps-long} [\/if]\r\n\r\n[MultipleMarkerMap z=\"12\" lat=\"{@gps-lat}\" lon=\"-{@gps-long}\" marker=\"{@gps-lat},-{@gps-long}\"] \r\n","type":"template","slug":"trail-characteristics","options":{"_edit_lock":"1537830350:2","_edit_last":"2","admin_only":"","restrict_capability":"","capability_allowed":"","pod_reference":"a:1:{s:3:\"pod\";s:5:\"trail\";}"}}}}

Workaround or Alternate Solution Until Bug is Addressed

Related Issues and/or PRs

I don’t know why I’m copied on these emails.

Thanks, Matt Roseboom Editor/Publisher Attractions Magazine 7512 Dr. Phillips Blvd. STE 50-612 Orlando FL 32819 Phone: (407) 741-3200 AttractionsMagazine.com http://attractionsmagazine.com/

On Jan 11, 2019, at 6:24 PM, vicmich notifications@github.com wrote:

Hi Scott

I admit “multiple values for inputs” is getting out of my depth here, and I don’t expect you to handhold me, but just wanted to note, I’ve queried wp_postmeta with:

SELECT post_id FROM wp_postmeta WHERE meta_key LIKE '%gps-long%' GROUP BY post_id HAVING count(post_id) > 1;

for both gps-lat and gps-long (which I guess you suggested I examine because they’re the only number fields(?)). And I’m getting zero results.

Does what I’ve done make sense to find the multiple values? As I say, I don’t expect to be coddled ;-), but want to know if I’m on right track.

Thanks very much for a great plugin and your help so far.

I’m going to be away all of next week, so will update my client and see if he’s okay with not doing any trail updates till I’m back and have had a chance to spend more time on it.

Thanks!

Vic

From: Scott Kingsley Clark [mailto:notifications@github.com] Sent: Thursday, January 10, 2019 10:50 PM To: pods-framework/pods Cc: vicmich; Author Subject: Re: [pods-framework/pods] Fatal error: Unsupported operand types with v2.7.12 (#5269)

It sounds like an error related to a custom field having multiple values. That's not yet supported by Pods, so it may have been inserted inadvertently by another plugin or someone with access to the database. One thing to look out for in your database is the values for each gps-lat and gps-long. It appears some trails may have multiple meta_value records in your wp_postmeta table. Clear those up and the error will go away.

Just FYI -- we are adding official support for repeatable fields (multiple values for inputs, apart from Relationships) in 2.9, but right now we are in development with Pods 2.8 to add support for multiple groups of fields. We won't support multiple values for fields in our forms until Pods 2.9.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/pods-framework/pods/issues/5269#issuecomment-453369241 , or mute the thread https://github.com/notifications/unsubscribe-auth/ABWj9Ue8DPrQBPD2Mcxa7WXaKbQ4XdJWks5vCAnUgaJpZM4Z6g-J . https://github.com/notifications/beacon/ABWj9ffoHZ-CvXVaDyBKr-MEQ81sEPL7ks5vCAnUgaJpZM4Z6g-J.gif

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/pods-framework/pods/issues/5269#issuecomment-453688922, or mute the thread https://github.com/notifications/unsubscribe-auth/AC3qqa3wn49rGG1vklJLcN7rnRQUeriJks5vCR09gaJpZM4Z6g-J.

pods-framework / pods