Skip Navigation

[Resolved] Update buttons grays out

This support ticket is created 3 years, 3 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)

This topic contains 5 replies, has 2 voices.

Last updated by Shane 3 years, 3 months ago.

Assisted by: Shane.

Author
Posts
#2360989

This issue was marked as resolved, but it has not been resolved. Please refer to this ticket for site access and info https://toolset.com/forums/topic/update-buttons-grays-out/

I am trying to: update page content

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

I expected to see: being able to update page

Instead, I got: grayed out update page, sometimes update button returns, sometimes it stays grayed out.

HTPASSWD ACCESS TO STAGING SITE:
U: foundry
P: foundry

#2361039

Shane
Supporter

Languages: English (English )

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

Hi Kyle,

Thank you for getting in touch.

The ticket was closed because there wasn't any activity on it for several days.

As per our previous discussion it would appear that there are some differences between your live site and your staging site.

Have you gotten any response from your hosting company?

Please let me know.

Thanks,
Shane

#2361083
Untitled-1.jpg

I understand, its just frustrating that the issue is marked as resolved when the issue is still present.

I checked with our hosting support team and confirmed that there are no AJAX requests timing out. The issue occurs on pages that have a section of conditional toolset code. It was built by a developer who doesn't work with us anymore and we don't have any notes on how it works. I'm wondering if there's something incorrect with the way this conditional code was written. If you see the attached screenshot, that's the area in question that you'll be able to see on the page I linked to this ticket.

This issue has been plaguing us and our client on a number of pages, we're really hoping we can find a resolution. Otherwise we are making website updates via SQL code haha.

#2361643

Shane
Supporter

Languages: English (English )

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

Hi Kyle,

I had a look on the content template that the view is loading and it appears that your template is loading some incomplete conditionals.

I'm unsure what field that the conditional should be checking for but if you can look at the template below and let me know if you have an idea then I could complete the conditionals for you.
hidden link

Thanks,
Shane

#2369563

Hi Shane,

That section is supposed to be pulling posts of post type "Agua Special" if they have a matching category that corresponds to the page title. We think the script is complete.

What section of the conditional is incomplete.

Regards,
Jake

#2370035

Shane
Supporter

Languages: English (English )

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

Hi Jake,

From what I checked the issue is definitely coming from the restaurant specials cards view block.

Specifically the content template you're using to display the items.

I would suggest here that you build a dedicated content template for this view and then re-add it rather than loading a content template for a different post type.

The reason for this is your view is listing out Pages but the content template is set to display on the "Agua Modules" post type.

The Pages and Agua Modules post type may not share the same data which can lead to conflicts. Having a dedicated content template for this view's data will allow you to better manage what is displayed for this particular view.

The moment I remove the content template from the view, the update button starts to work again.

Thanks,
Shane