Forum Replies Created

Viewing 7 replies - 16 through 22 (of 22 total)
  • Thread Starter Tom

    (@tomybyte)

    I’m sorry. You are right. The result was what I wrote above, but it seems that not the Loco plugin was responsable for the disaster. Fact is, that I installed Loco short before the damage happend. But I did right before some experiments, copied from another place, when I wanted to translate the role labels in the backend:
    https://wordpress.stackexchange.com/questions/92529/is-there-a-way-to-localize-role-labels
    It was very likely the code from Johannes Pille – I tried. It does not work anymore in fact of the changes in WP core. So I transformed it a little bit and that may have caused the problems. Sorry I really forgot this.

    Hi admin – I was too quick with my allegation – Loco is no monster, may be it is a good plugin even it did not help me translate the user role labels in the users view in the backend. Can I edit my posts and correct that?

    Tim, I want to apologize for my harsh words.

    Tom

    • This reply was modified 6 years ago by Tom. Reason: misspelling
    Thread Starter Tom

    (@tomybyte)

    I’ve got the monster, that caused the trouble.

    It was the loco translator plugin:

    I detected that in the database of the corrupted website in the wp_options table the options_name key wp_user_roles had been everything deleted inspite of this: a:1:{s:10:”translator”;a:2:{s:4:”name”;s:10:”Translator”;s:12:”capabilities”;a:3:{s:4:”read”;b:1;s:10:”loco_admin”;b:1;s:12:”upload_files”;b:1;}}}

    So nothing worked any more, even not my plugin user specific functions and class methods.
    After updating the wp_user_roles key with the backup data, everything is back, even the wp-admin access.

    So I have to state: I won’t use the loco plugin any more – it is worse!!

    • This reply was modified 6 years ago by Tom. Reason: misspelling
    • This reply was modified 6 years ago by Tom. Reason: misspelling
    Thread Starter Tom

    (@tomybyte)

    Sorry at first I didn’t discover that for import it is possible to select a different delimiter in the option section of Woocommerce product import.
    That is working better than expected.
    It would be great if the same would be possible for export, but that is not so important for me.

    Thread Starter Tom

    (@tomybyte)

    errror correction: The most descriptions …

    Thread Starter Tom

    (@tomybyte)

    Hi Frank,

    I’m using Version 1.1.1 of your testimonial slider plugin, that’s working fine. Version 1.1.2 doesn’t work as I mentioned above. If you got results about the newer version, then let me know.

    Best regards

    Tom

    Thread Starter Tom

    (@tomybyte)

    It is a selfmade theme.
    The System is using WPML.
    Multilanguage support is added to testimonal posttype. That is perfect working.
    I insert the shortcode in function.php here
    function t3_add_testimonial_genesis_slider(){
    if (is_front_page()){

    echo ‘<div class=”testimonial-slider”><div class=”wrap”><h3>’;
    if (ICL_LANGUAGE_CODE == “de”) {
    echo DE_TESTIMONIAL_TITLE;
    }else{
    echo EN_TESTIMONIAL_TITLE;
    }
    echo ‘</h3>’;
    do_shortcode(‘[gts-slider]’);
    echo ‘</div></div>’;
    }
    }
    In Version 1.1.1 the slider will be displayed in version 1.1.2 not.

    Thread Starter Tom

    (@tomybyte)

    So bad, there is apparently no professional solution!

Viewing 7 replies - 16 through 22 (of 22 total)