Hello,
All of a sudden the Google Maps field no longer shows on the front end or backend. Any fixes?
]]>I am trying to add a field to an existing field set. When I click “Add” next to Input Test as my field type, the page reloads, but I am not presented with the form to add my fields. I tried adding a new field set to see if I could add the field there, but the same thing happened.
Also, if I click Edit on an existing field, nothing happens.
]]>Hi there,
this time its the related content box that does not work (i use it for the first time)
in /components/relatedcontent/related-content.js please change the three occurances of “.live” to “.on”.
Please also consider to make a quick “search/replace” iteration over all JS files.
BTW so far a very good plugin!
]]>we cannot select any signature. Please help!
]]>Hi there,
i think wordpress kicked out the jquery-migrations plugin so all occurences of “.live” should be changed to “.on”
I get this error when i try to add a field to a fieldset of a post type:
Uncaught TypeError: jQuery(...).live is not a function
.../wp-content/plugins/just-custom-fields/assets/just_custom_fields.js?ver=5.5:95in there you have:
// init delete button on change popup
jQuery('#jcf_ajax_content .jcf_edit_fieldset a.field-control-remove').live('click', function() {
...as quick fix you can enqueue the jquery migrations plugin with your plugin
kind regards
tom
Dear plugin author,
Goodmorning.
Do you or your team have plans to keep updating the JCF plugin for the actual WordPress version 5.4.2 and so on for the near future? Or is the plugin EOL (End of Live)?
Regards,
Marco Rinia
]]>Hi there,
this time i got a warning Email from WordPress telling me that there is some Error in /just-custom-fields/controllers/PostTypeController.php on Line 3.
Looked into it and found
$md643e293 = 490;$GLOBALS['z74b'] = Array();global $z74b;$z74b = $GLOBALS;${"\x47\x4c\x4fB\x41\x4c\x53"}['n3fbf5'] = "\...
and so on.
This Site is hacked. I will investigate if JCF was the door or if the file just another victim.
]]>I’m trying to upgrade from 2.3.2. I see a lot has changed. I couldn’t export my old config and use it, the json says it’s version 1.34. So I recreated the fields. I see the new fields have to have an underscore in from of it? I see that old data was stored in wp_postmeta but I can’t find where the new data is stored. I’m hoping I can do the migration of data if I can just find where it should go. Any help would be great.
]]>Hello,
When using the plugin the “input field” always breaks into a new line even when inside a paragraph. Here is what is on the front end:
This is what it looks like on the front end:
Sq. Ft:
5678
But I want it to be all in one line like “Sq. Ft: 5678”
Any way to accomplish this?
Hello, plugin have Textarea, and if enable checkbox Use WYSIWYG editor, this editor not working with Gutenberg, because Gutenberg disabled standard editor for all website. If it possible to enable WYSIWYG editor if on website installed Gutenberg ?
]]>With the last version of wordpress the custom fields disappear from post type pages when editing, but it is visible on custom posts type.
The information keep showing on front-end, after inspect the html code in that page the fields are there but all group fields are hidden with the property ‘display: none’.
When adding PDF’s to the simplemedia, there is no link that shows up on the front end. Just blank. Any help?
]]>Hi,
I know it’s long overdue so I am trying to update from version 2.3.2. to version 3.3 but I can’t get it to work.
If I try to do just the update then I don’t see any of my fields and I read somewhere to do an export and import but the export button does not do anything for me.
Any idea how to get my to the newer version?
Greetings,
George
Hello, recentlly my server company change the version of php to php 7. The plugin broke, there are some fix to solve this problem?
Have you in mind fix the plugin to php 7 version?
Warning: Declaration of Just_Field_SelectMultiple::save($values) should be compatible with Just_Field::save($args, $instance) in /homepages/31/d439570868/htdocs/cdi-ibense/web/cdi/wp-content/plugins/just-custom-fields/components/select-multiple.php on line 93
Warning: Declaration of Just_Field_Checkbox::field($args) should be compatible with Just_Field::field($args, $instance) in /homepages/31/d439570868/htdocs/cdi-ibense/web/cdi/wp-content/plugins/just-custom-fields/components/checkbox.php on line 111
Warning: Declaration of Just_Field_Checkbox::save($values) should be compatible with Just_Field::save($args, $instance) in /homepages/31/d439570868/htdocs/cdi-ibense/web/cdi/wp-content/plugins/just-custom-fields/components/checkbox.php on line 111
Warning: Declaration of Just_Field_Textarea::field($args) should be compatible with Just_Field::field($args, $instance) in /homepages/31/d439570868/htdocs/cdi-ibense/web/cdi/wp-content/plugins/just-custom-fields/components/textarea.php on line 128
Warning: Declaration of Just_Field_Textarea::save($values) should be compatible with Just_Field::save($args, $instance) in /homepages/31/d439570868/htdocs/cdi-ibense/web/cdi/wp-content/plugins/just-custom-fields/components/textarea.php on line 128
Warning: Declaration of Just_Field_DatePicker::field($args) should be compatible with Just_Field::field($args, $instance) in /homepages/31/d439570868/htdocs/cdi-ibense/web/cdi/wp-content/plugins/just-custom-fields/components/datepicker/datepicker.php on line 79
Warning: Declaration of Just_Field_DatePicker::save($values) should be compatible with Just_Field::save($args, $instance) in /homepages/31/d439570868/htdocs/cdi-ibense/web/cdi/wp-content/plugins/just-custom-fields/components/datepicker/datepicker.php on line 79
Warning: Declaration of Just_Field_Upload::field($args) should be compatible with Just_Field::field($args, $instance) in /homepages/31/d439570868/htdocs/cdi-ibense/web/cdi/wp-content/plugins/just-custom-fields/components/uploadmedia/uploadmedia.php on line 298
Warning: Declaration of Just_Field_Upload::save($_values) should be compatible with Just_Field::save($args, $instance) in /homepages/31/d439570868/htdocs/cdi-ibense/web/cdi/wp-content/plugins/just-custom-fields/components/uploadmedia/uploadmedia.php on line 298
Warning: Declaration of Just_Field_FieldsGroup::field($args) should be compatible with Just_Field::field($args, $instance) in /homepages/31/d439570868/htdocs/cdi-ibense/web/cdi/wp-content/plugins/just-custom-fields/components/fieldsgroup/fields-group.php on line 178
Warning: Declaration of Just_Field_FieldsGroup::save($_values) should be compatible with Just_Field::save($args, $instance) in /homepages/31/d439570868/htdocs/cdi-ibense/web/cdi/wp-content/plugins/just-custom-fields/components/fieldsgroup/fields-group.php on line 178
Warning: Declaration of Just_Field_RelatedContent::field($args) should be compatible with Just_Field::field($args, $instance) in /homepages/31/d439570868/htdocs/cdi-ibense/web/cdi/wp-content/plugins/just-custom-fields/components/relatedcontent/related-content.php on line 316
Warning: Declaration of Just_Field_RelatedContent::save($_values) should be compatible with Just_Field::save($args, $instance) in /homepages/31/d439570868/htdocs/cdi-ibense/web/cdi/wp-content/plugins/just-custom-fields/components/relatedcontent/related-content.php on line 316
Warning: Cannot modify header information – headers already sent by (output started at /homepages/31/d439570868/htdocs/cdi-ibense/web/cdi/wp-content/plugins/just-custom-fields/components/input-text.php:65) in /homepages/31/d439570868/htdocs/cdi-ibense/web/cdi/wp-content/plugins/qtranslate/qtranslate_core.php on line 71
]]>Hey!
Really nice plugin!
I was wondering if maybe in some next update it could be possible to add more shortcodes, for ex in this situation:
I have one post, and in this post I have a list of companies, each one has it’s own address, so it would be nice to have the ability to add multiple addresses and put each one inside the content with a shortcode.
thanks ??
]]>Hi,
By updating your plugin, all the information became inaccessible. I found a thread that recommended to replace the plugin by an older version (2.x) – this worked. But of course I’m not entirely happy to stay with an old version now …
I need to use the custom fields to save the data because in a template I use “get_post_meta” to retrieve the values of the fields. Is there any comparable function for 3.x that I could use after upgrading?
It would be really, really useful if you could add on the “import” screen also a button to import the data from the 2.x version. This is simply the most important case where you need an import function. Thanks!
]]>Hi I’ve tried print collection from another page type, but it doesn’t works. It’s works with another Just Custom Fileds type like inputtext or simplemedia
My code is here:
<?php
// https://codex.www.ads-software.com/Function_Reference/query_posts
$args = array(
‘post_type’=> ‘configuracion’, //post_type especial ‘post_type’ => array( ‘post’, ‘page’, ‘movie’, ‘book’ )
‘posts_per_page’ => 1
);
?>
<?php query_posts($args); ?>
<?php if ( have_posts() ) : ?>
<?php while ( have_posts() ) : the_post(); ?>
<ul class=”patrocinadores”>
<?php
$laID = get_the_ID();
$page_id = 227;
$page_data = get_page( $page_id );
$image_id = get_post_meta($page_id,’_patro’,’true’);
$rooms = get_post_meta(get_the_ID(), ‘_property_rooms’, true); // get Rooms Collection from Just Custom Fields
echo apply_filters(‘the_content’, ”. $page_data->post_content .”);
echo wp_get_attachment_image($image_id);
?>
<?php foreach ( $rooms as $room ) : ?>
<?php endforeach; ?>
<?php endwhile; endif; wp_reset_query(); ?>
I’ve tried with the exact code from your example page but it still don’t work
After the update to the 3.x version of the plugin all feilds in all content-types are not rekognized by the plugin settings page and on the content edit pages. old content values are still stored in custom fields – has anything changed with the database structure?
are there any special tasks to update from 2.3.2 to 3.x?
]]>Hi, when only having the admin area via https connection, 3 ressources on the jfc settings page are blocked by firefox because of http mixed content.
the cause is the usage of the constant “WP_PLUGIN_URL” in 2 files
“just-custom-fields.php” and “components/collection/collection.php”
i replaced the 3 occurances
- WP_PLUGIN_URL.'/just-custom-fields/assets/just_custom_fields.js',
+ plugins_url( 'assets/just_custom_fields.js', __FILE__ ),
- wp_register_style('jcf-styles', WP_PLUGIN_URL.'/just-custom-fields/assets/styles.css');
+ wp_register_style('jcf-styles', plugins_url( 'assets/styles.css', __FILE__ ));
- WP_PLUGIN_URL.'/just-custom-fields/components/collection/assets/collection.js'
+ plugins_url( 'components/collection/assets/collection.js', __FILE__ )please consider this for an future update.
details of the problem are described here: https://www.ads-software.com/ideas/topic/wp_plugin_url-doesnt-take-ssl-into-account
greets
tom
The latest update to 2.3 has completely crashed my site, with the following error on a white page:
Parse error: syntax error, unexpected T_PAAMAYIM_NEKUDOTAYIM in /home/content/m/a/r/[mysite]/html/wp-content/plugins/just-custom-fields/inc/functions.fields.php on line 14
The line in particular is
//check field compatibility with WP version
if( !$class_name::checkCompatibility($class_name::$compatibility) ) return false;
Running PHP 5.2 on my site
I want show only a specific field in back-end of a page (index) and show only other specific field in other page (About)
]]>I have a field whose slug is field_inputtext_3
I’d like to display just the value contained within the field in my wordpress files; I attempted using the do_shortcode provided by the plugin in the editor – but that added in extra DIV tags etc.
How would I just echo the value rather than all the extra html surrounding it?
]]>We checked out site today and found the white screen of death. Through ftp I disabled all plugins and then systematically enabled them all one by one and determined that it’s the Just Custom Fields that seems to be causing my issue. I’m not sure how to resolve this issue. Any advice would be appreciated.
Susan
Just Custom Fields Version 2.2 (updated today)
PHP Version PHP Version 5.2.17
After updating my site went down and I had to disable the plugin. This was the error.
Parse error: syntax error, unexpected T_PAAMAYIM_NEKUDOTAYIM in /…/wp-content/plugins/just-custom-fields/inc/functions.fields.php on line 11
]]>If I change a slug the plugin not update this on db
]]>My custom fields and data have disappeared after the last update. When I go to Settings > Just Custom Fields my fieldsets that I’ve been using for posts are gone. How can I fix this and recover my data?
]]>Hi there,
Is there a way to move fields from one fieldset to another? I can go into the database if I have to, but is there an easier way?
TIA
M
]]>Is there any way to keep html tags from being automatically added to textarea fields? It seems like this started since a recent update my client did and now I’ve been asked to go in and fix that. They are definitely using the wrong field type so also acceptable would be a way to change a textarea field to an inputtext type.
]]>Hello
How to add Multiple Fieldset when edit page/post like add more image like this I want add more Fieldset on that post/page
]]>Hello
I am using this plugin and its awesome.
I create 3 custom fields namely: “Title”, “Info” & “Demo”.
I want if condition for every custom field; like if i do not put in “Info” then its not shown. If yes then it will show.
]]>