netzgestaltung

i think you can be more polite as you are using a free and open plugin.

you even couldt digg into it and write a patch…

it also worked on pages where i previouly used my script to get the migration faster.

tested with fields: datepicker, textarea, inputtext and checkbox.

tested and works like a charm – i got a notice that there are old settings and that it will import it.

afterwards, fields and settings where there – i tested only with text fields!

good job!

I have the same problem – did you get it fixed somehow?

it simply is a great plugin, but i fear it will not stay at this status.

• This reply was modified 8 years ago by netzgestaltung.

you really could thank me by taking out the spam message from the plugin, which affect dozends of my sites and admins, that may not know they allready have another login security plugin or at least make the message look more like a commecial than a security message.

well so maybe i will fork it in the next days and make my own of it without commercials.

try

!(is_page(9) || is_single(10))

@kelmas

there seems to be 3 more spam functions in it ‘widget_logic_promo’, ‘widgel_logic_dissmiss_promo’ (note the typo) and ‘widget_logic_promo_scripts’.

what a cheap way forcing spam to 300000 admin users with a missleading security message

• This reply was modified 8 years ago by netzgestaltung.

sorry, seems that it wasnt you ??

taking it over is one thing, adding $promo at the first overtaken version is something different…. ??

what the hack?

that sounds good, also the migration of the upload media field.

in while im done with the json output which seems to should import on the new versions (tested on a simple page)

function old_jcf_settings($output_json = true){
  $post_types = get_post_types();
  $post_types_objects = get_post_types(null, null, 'objects');
  $jcf_fieldsets = 'jcf_fieldsets-';
  $jcf_fields = 'jcf_fields-';
  $jcf_settings = [];
  $new_jcf_settings = [];
  
  foreach ( $post_types as $post_type ) {
    $post_fieldsets = get_option($jcf_fieldsets . $post_type);
    $post_fields = get_option($jcf_fields . $post_type);
    
    if ( $post_fieldsets || $post_fields ) {
      $jcf_settings[$post_type] = [];
      if ( $post_fieldsets ) {
        $jcf_settings[$post_type]['fieldsets'] = $post_fieldsets;
        $new_jcf_settings['fieldsets'][$post_type] = array_merge(
          array('position' => null,'priority' => null),
          $post_fieldsets
        );
        foreach ( $post_fieldsets as $post_fieldset_id => $post_fieldset ) {
          $post_fieldset_fields = $post_fieldset['fields'];
          foreach ( $post_fieldset_fields as $post_fieldset_field => $enabled ) {
            $jcf_settings[$post_type]['fieldsets'][$post_fieldset_id]['fields'][$post_fieldset_field] = array_merge(
              $post_fields[$post_fieldset_field],
              array('enabled' => $enabled)
            );
          }
        }
      }
      if ( $post_fields ) {
        $new_jcf_settings['fields'] = [];
        $new_jcf_settings['fields'][$post_type] = $post_fields;
      }
      $new_jcf_settings['post_types'][$post_type] = $post_types_objects[$post_type];
    }
  }
  if ( $output_json ) {
    echo '<!-- old_jcf_settings: ', "\r\n";
    echo json_encode($jcf_settings), "\r\n";
    echo ' -->', "\r\n";
    
    echo '<!-- new_jcf_settings: ', "\r\n";
    echo json_encode($new_jcf_settings), "\r\n";
    echo ' -->', "\r\n";
  } else {
    echo '<!-- old_jcf_settings: ', "\r\n";
    echo var_dump($jcf_settings), "\r\n";
    echo ' -->', "\r\n";
    
    echo '<!-- new_jcf_settings: ', "\r\n";
    echo var_dump($new_jcf_settings), "\r\n";
    echo ' -->';
  }
}

just copy the “new_jcf_settings” output line in a json file and import.

• This reply was modified 8 years, 1 month ago by netzgestaltung.

for now i made a small script, displaying the old settings while having the new version activated, so conversion runs much faster now.

for the functions.php:

<php

function old_jcf_settings(){
  $post_types = get_post_types();
  $jcf_fieldsets = 'jcf_fieldsets-';
  $jcf_fields = 'jcf_fields-';
  $jcf_settings = [];
  
  foreach ( $post_types as $post_type ) {
    $post_fieldsets = get_option($jcf_fieldsets . $post_type);
    $post_fields = get_option($jcf_fields . $post_type);
    
    if ( $post_fieldsets || $post_fields ) {
      $jcf_settings[$post_type] = [];
    
      if ( $post_fieldsets ) {
        $jcf_settings[$post_type]['fieldsets'] = $post_fieldsets;
      }    
      if ( $post_fields ) {
        $jcf_settings[$post_type]['fields'] = $post_fields;   
      }
    }
  }
  echo '<!-- old_jcf_settings: ', var_dump($jcf_settings), ' -->';     
}

?>

and then call it in any template file (example for page.php).

<?php
  if ( is_page('test_custom_fields') ) {
    old_jcf_settings();
  }

?>

its only displaying in the output source code, so the normal view isn’t disturbed while viewing. converting the output to json seems not so much effort, i just actually don’t know the structure of an import/export json file.

hi, im currently working on a solution, that reads out the meta field names and inserts new fields into the new version of jcf – do you actually work on this? should i wait?