sierrajoe
Member
Posted 1 year ago #
I have been using custom fields template for a few weeks and it has worked as expected. Yesterday I tried adding a new post with a custom fields template that included a "file" field and it would not work. When I entered the file path using the browse button, the "save" button would gray out and become unusable. If I tried to "save draft" I would get an error:
Catchable fatal error: Object of class WP_Error could not be converted to string in /formatting.php on line 1229
So, now I can no longer add a file using the custom field template...
If you have any idea what could cause this please let me know... getting desparate!
joe
I have the same problem.
The save button of CFT is enabled at first but as soon as I add a file through the browse button it is disabled and grayed out.
It happenend a couple of weeks ago and behaves the same in both WP 3.0 and 2.9.
Saving with the standard WP "Publish" button will just reset the fields.
I'm in the same boat, any help on this would be greatly appreciated.
Steve
Because the javascript file upload is difficult to handle, if you sellect the file, you can not push the cft save button. It is a normal action. However, I am not sure why PHP code error occurs when you push the save draft button. Let me know the more detail steps which the error occurs. Thanks.
sierrajoe
Member
Posted 1 year ago #
I solved this problem by making my file types acceptable as wordpress uploads by editing the wp_ext2type() and get_allowed_mime_types() functions in the wp-includes/functions.php file. I probably should have left these functions alone and added the modified versions to my theme's functions.php and in fact will do that now.
joe
sierrajoe
Member
Posted 1 year ago #
whoops... spoke too soon... modifying my theme's functions.php did not work so I'll live with the hacked core for now.
joe
sierrajoe
Member
Posted 1 year ago #
OK, I had to figure out the proper way to add custom upload mime types before I upgraded to wp 3.01... I found this recommendation and it seems to have worked for me. I made the changes suggested to my theme's functions.php and then did the upgrade. all went well.
joe