Skip Navigation

[Resolved] One CPT does not display following update to 3.3.11

This support ticket is created 4 years, 7 months ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Sun Mon Tue Wed Thu Fri Sat
- 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 -
- 13:00 – 18:00 13:00 – 18:00 13:00 – 18:00 14:00 – 18:00 13:00 – 18:00 -

Supporter timezone: America/Jamaica (GMT-05:00)

Tagged: 

This topic contains 9 replies, has 2 voices.

Last updated by Shane 4 years, 7 months ago.

Assisted by: Shane.

Author
Posts
#1672055

I am trying to:
Display Barrels on this page

Link to a page where the issue can be seen:
hidden link

I expected to see:
When the site was update to 3.3.11 of Tools, the barrels do not display

Instead, I got:
The message to say there were none found

All the other CPT (right side menu, for example 'Rifles and Actions' display fine!

The pages are using Beaver Builder Page Builder, with 'Views' to display on the respective pages.
I removed 3.3.11 and went back to 3.3.10 and the listing shows all the entries (obviously I have left it like that for now!)

TIA, Dave

#1672595

Shane
Supporter

Languages: English (English )

Timezone: America/Jamaica (GMT-05:00)

Hi David,

Thank you for getting in touch.

Would you mind allowing me to have admin access to the website so that I can have a look at this for you.

The private fields have been enabled for your next response.

Thanks,
Shane

#1673595

Shane
Supporter

Languages: English (English )

Timezone: America/Jamaica (GMT-05:00)

Screenshot 2020-06-23 at 9.18.22 AM.png

Hi David,

Thank you for the credentials.

I looked at this for you and the page displays the Barrels. See Screenshot

They display fine to me.

Thanks,
Shane

#1674089

Of course they do, did you read this above ?

"I removed 3.3.11 and went back to 3.3.10 and the listing shows all the entries (obviously I have left it like that for now!)"

Did you look to see that 3.3.10 is being used in the plugin list ?

#1674939

Shane
Supporter

Languages: English (English )

Timezone: America/Jamaica (GMT-05:00)

Hi David,

Thank you for the clarity,

I will be installing the newer version as a test to replicate the issue.

Thanks,
Shane

#1675015

Shane
Supporter

Languages: English (English )

Timezone: America/Jamaica (GMT-05:00)

Hi David,

Thank you for the patience, it seems this issue was due to caching. When you activate the latest version of Types it was using a completely different custom field slug for the filter.

Once I cleared the cache it started to work.

Please let me know if this helps.
Thanks,
Shane

#1678605

OK so I noticed 3.3.10 is still the current version installed - did you update it to 3.3.11 see it was fixed after you cleared the cache and then put it back to 3.3.10 ?

It just seemed odd that you would not leave it on 3.3.11 if it was working fine ?

Let me know...

Dave

#1680351

Shane
Supporter

Languages: English (English )

Timezone: America/Jamaica (GMT-05:00)

Hi Dave,

I Did leave it on 3.3.11

When you check the active Types plugin you will see that Types version 3.3.11 is active.

Thanks,
Shane

#1680527

Sorry Shane, you are correct - the reason is, I saw an entry in the plugins list that shows 3.3.10
But that must be a backup in the plugins folder.
I'll remove it..
Kind regards, dave

#1681031

Shane
Supporter

Languages: English (English )

Timezone: America/Jamaica (GMT-05:00)

Hi Dave,

Actually I would recommend that you disable 3.3.11 that I installed and then perform the normal upgrade procedure to bring your 3.3.10 up to the latest version.

This is because I installed version 3.3.11 under a different folder name than the default. This is to ensure that you don't have 2 duplicates of the Types plugin on your site.

Once you have done this then you can go ahead and mark this ticket as resolved.

Thanks,
Shane