Skip Navigation

[Resolved] Custom Fields Admin Page Doesn't Load

This support ticket is created 6 years, 4 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
8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 - -
13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 - -

Supporter timezone: America/New_York (GMT-04:00)

This topic contains 5 replies, has 2 voices.

Last updated by Christian Cox 6 years, 4 months ago.

Assisted by: Christian Cox.

Author
Posts
#1129270
2018-10-17_16-47-06.jpg

I am trying to: set up custom fields for my custom post type.

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

The page doesn't load. I just get a constant pre-loader (grab attached)

Thanks

Phil

#1129295

Hi, I can see from your debug information that your site uses the Enfold theme. There are several critical compatibility issues between Toolset and Enfold, and we have reached out to their developers multiple times to try to collaborate on solutions. So far we haven't received any assistance. I encourage you to reach out to the theme authors and let them know we have tried to start a dialog about compatibility fixes, but haven't received any feedback.

As a quick test you could temporarily switch to a default theme like Twenty Seventeen and retest. If the problem is resolved, it's a conflict with Enfold causing this problem. If not, continue with the following troubleshooting steps:
- Deactivate all plugins except Types and retest. If the problem was resolved, reactivate your other plugins one by one until the problem returns.
- If the problem is not resolved, clear your browser cache and reload the page. Open the browser console and check to see if any JavaScript errors are displayed.
Let me know the results of these tests and we can go from there.

#1129300

Hi,

I've switched to 2017 theme, disabled all plugins except the 4 Toolset plugins and am still getting the same issue.

My console shows 5 errors

head.min.js?ver=3.2.3:12 GET <em><u>hidden link</u></em> net::ERR_ABORTED 404
q @ head.min.js?ver=3.2.3:12
t @ head.min.js?ver=3.2.3:11
(anonymous) @ head.min.js?ver=3.2.3:14
m @ head.min.js?ver=3.2.3:10
d.load @ head.min.js?ver=3.2.3:14
self.loadDependencies @ main.js?ver=3.1.2:165
self.init @ AbstractPageController.js?ver=3.2.3:276
r @ head.min.js?ver=3.2.3:10
(anonymous) @ head.min.js?ver=3.2.3:16
m @ head.min.js?ver=3.2.3:10
(anonymous) @ head.min.js?ver=3.2.3:16
r @ head.min.js?ver=3.2.3:10
(anonymous) @ head.min.js?ver=3.2.3:12
m @ head.min.js?ver=3.2.3:10
p @ head.min.js?ver=3.2.3:12
c @ head.min.js?ver=3.2.3:13
17:40:59.615 head.min.js?ver=3.2.3:12 GET <em><u>hidden link</u></em> net::ERR_ABORTED 404
q @ head.min.js?ver=3.2.3:12
t @ head.min.js?ver=3.2.3:11
(anonymous) @ head.min.js?ver=3.2.3:14
m @ head.min.js?ver=3.2.3:10
d.load @ head.min.js?ver=3.2.3:14
self.loadDependencies @ main.js?ver=3.1.2:165
self.init @ AbstractPageController.js?ver=3.2.3:276
r @ head.min.js?ver=3.2.3:10
(anonymous) @ head.min.js?ver=3.2.3:16
m @ head.min.js?ver=3.2.3:10
(anonymous) @ head.min.js?ver=3.2.3:16
r @ head.min.js?ver=3.2.3:10
(anonymous) @ head.min.js?ver=3.2.3:12
m @ head.min.js?ver=3.2.3:10
p @ head.min.js?ver=3.2.3:12
c @ head.min.js?ver=3.2.3:13
17:41:00.110 head.min.js?ver=3.2.3:12 GET <em><u>hidden link</u></em> net::ERR_ABORTED 404
q @ head.min.js?ver=3.2.3:12
t @ head.min.js?ver=3.2.3:11
(anonymous) @ head.min.js?ver=3.2.3:14
m @ head.min.js?ver=3.2.3:10
d.load @ head.min.js?ver=3.2.3:14
self.loadDependencies @ main.js?ver=3.1.2:165
self.init @ AbstractPageController.js?ver=3.2.3:276
r @ head.min.js?ver=3.2.3:10
(anonymous) @ head.min.js?ver=3.2.3:16
m @ head.min.js?ver=3.2.3:10
(anonymous) @ head.min.js?ver=3.2.3:16
r @ head.min.js?ver=3.2.3:10
(anonymous) @ head.min.js?ver=3.2.3:12
m @ head.min.js?ver=3.2.3:10
p @ head.min.js?ver=3.2.3:12
c @ head.min.js?ver=3.2.3:13
17:41:00.843 head.min.js?ver=3.2.3:12 GET <em><u>hidden link</u></em> net::ERR_ABORTED 404
q @ head.min.js?ver=3.2.3:12
t @ head.min.js?ver=3.2.3:11
(anonymous) @ head.min.js?ver=3.2.3:14
m @ head.min.js?ver=3.2.3:10
d.load @ head.min.js?ver=3.2.3:14
self.loadDependencies @ main.js?ver=3.1.2:165
self.init @ AbstractPageController.js?ver=3.2.3:276
r @ head.min.js?ver=3.2.3:10
(anonymous) @ head.min.js?ver=3.2.3:16
m @ head.min.js?ver=3.2.3:10
(anonymous) @ head.min.js?ver=3.2.3:16
r @ head.min.js?ver=3.2.3:10
(anonymous) @ head.min.js?ver=3.2.3:12
m @ head.min.js?ver=3.2.3:10
p @ head.min.js?ver=3.2.3:12
c @ head.min.js?ver=3.2.3:13
17:41:00.844 main.js?ver=3.1.2:176 Uncaught TypeError: Types.page.customFields.viewmodels.ListingViewModel is not a constructor
    at Types.page.customFields.Class.self.getMainViewModel (main.js?ver=3.1.2:176)
    at self.initMainViewModel (AbstractPageController.js?ver=3.2.3:254)
    at Types.page.customFields.Class.self.initMainViewModel (ListingPageController.js?ver=3.2.3:24)
    at AbstractPageController.js?ver=3.2.3:277
    at r (head.min.js?ver=3.2.3:10)
    at head.min.js?ver=3.2.3:14
    at head.min.js?ver=3.2.3:11
    at HTMLScriptElement.e.onerror (head.min.js?ver=3.2.3:12)

I'm baffled.

I'm running this staging version on Siteground using their staging server CPanel tool using hidden link as the staging subdomain. But the settings uses the production domain, hidden link - this makes it easier to push changes from staging to prod. Could that be the cause?

Regards

Phil

#1129975

Yes, that's the problem. This required asset file (among others) is 404 in production:
hidden link

So if you want to use the production file paths in staging during testing, you should install the Types plugin in production. You can leave the plugin deactivated, so it doesn't affect the live site.

#1129981

Thanks Christian. I didn't think of that. I'll do that now.

Cheers

Phil

#1130015

Okay let me know if the problem is not resolved and I can take a closer look.