The edit pages for some of my custom posts have custom fields that are not working, and certain front-end scripts don't seem to be working only on a few posts, others are working fine. All these posts are using the same template file.
I have an image custom field added to my custom post type, and it allows multiple images. It seems like a javascript error is causing the "Add image" button to not trigger the action and add another field.
This action worked before I changed the name of my custom post type. Do I need to re-save the connection between the custom post type and the custom post fields? Will that refresh it and make it work again?
I've attached a screenshot of the console error I'm getting.
Let me know if you'd like to login to the site and take a look. Thank you.
Thank you for contacting Toolset Support. I am happy to help you with this.
This action worked before I changed the name of my custom post type. Do I need to re-save the connection between the custom post type and the custom post fields?
Please re-save the connection and let me know if this resolves the issue.
What was the name of the custom post type before and after?
I tried re-saving the custom post type and custom post fields, but it hasn't helped.
The name of the custom post type before was: "projects". The name now is "project"
I changed it so I could have better permalink urls. The name "projects" was in conflict with a page called Projects that used a template with a special loop, so I used "project" instead for the custom post type.
Now, any new "project" posts that are created don't work correctly.
Any idea what could be wrong?
Do you mind if I login and take a look?
I would like to request temporary access (wp-admin and FTP) to your site to take better look at the issue. You will find the needed fields for this below the comment area when you log in to leave your next reply. The information you will enter is private which means only you and I can see and have access to it.
Our Debugging Procedures
I will be checking various settings in the backend to see if the issue can be resolved. Although I won't be making changes that affect the live site, it is still good practice to backup the site before providing us access. In the event that we do need to debug the site further, I will request to duplicate the site and work in a separate, local development environment to avoid affecting the live site.
Privacy and Security Policy
We have strict policies regarding privacy and access to your information. Please see:
https://toolset.com/toolset-support-policy/privacy-security-providing-debug-information-support/
**IMPORTANT**
- Please make a backup of site files and database before providing us access.
- If you do not see the wp-admin/FTP fields this means your post & website login details will be made PUBLIC. DO NOT post your website details unless you see the required wp-admin/FTP fields. If you do not, please ask me to enable the private box. The private box looks like this:
hidden link
Thank you for that information. I am looking into the issue and will respond shortly after investigating.
Just a quick update to let you know I am still debugging on my end. Thank you for your patience.
"It is a testing site, but please ask before making any significant changes."
After some debugging, I would like to rule out plugin updates. Jetpack and Toolset Views need to be updated. May I do that?
Yes go right ahead and update those plugins.
Thank you for looking into this!
I also thought deleting the 'project' custom post type (and maybe all of the associated posts) and recreating all of them again may fix it since the problem only started once I renamed the custom post type. What do you think?
I don't think that will be necessary. 🙂 I updated Views and that did the trick.
Please let me know if this resolves the issue or if it needs more investigation.
Awesome! Thank you so much! Such a simple fix. Thanks for looking into it!
