Forum Replies Created

Viewing 13 replies - 1 through 13 (of 13 total)
  • Thread Starter tredneb

    (@tredneb)

    Ok, solution in CSS also does not work – when scrolling to next image, the images are offset incorrectly.

    Switching off Woocommerce in Astra Pro – reverting to the old style.

    To reproduce, use the vertical Gallery layout for single product.

    As an addition – I would like to select on the product itself whether I want the parent product to be visible.

    Many of my variable products have variations on Language or size – only some products have variations on color; and even for those I do not want to show them all as variable products. In the current solution I would need to add all the products I want to show the parent product for in the “Exclude from hide variable” field.

    In my case I would be looking for the following options:
    – Variable product with two languages => show parent product only;
    – Variable product with two colors => show both as single product and hide variable parent product;
    – Variable product with two colors and 5 sizes => show two single products (one for each color) and hide variable parent product;
    – Variable product with 5 colors and 5 sizes => show only (variable) parent product

    It might be an option to exclude specific attributes from generating single products (this would not enable my last option above, but might be easier to implement).

    • This reply was modified 4 years, 7 months ago by tredneb.

    As a workaround: I’ve disabled the metaboxes for the content types post and page, I´m now able to edit the posts normally – however, the Yoast meta box is unavailable.

    • This reply was modified 7 years, 4 months ago by tredneb.

    I´ve had the same issue with Chrome and Firefox on multiple sites when using the classic editor. The only option is deactivating Yoast before editing (which is I cannot advice my customers to do).

    The whole edit window freezes for pages and posts – even the tabs at the right-hand top will no longer respond.

    Thread Starter tredneb

    (@tredneb)

    I can confirm that it is resolved – can see the Blog Grid widget again in the newest version of the plugin.

    Thread Starter tredneb

    (@tredneb)

    There is probably a conflict with an other plugin. I tried dongrading, but that didn’t resolve it. I see that the plugin is included in the installation files, it is however not available to be activated.

    Thread Starter tredneb

    (@tredneb)

    Issue was caused by Polylang – and I was able to resolve it.

    In Polylang you explicitly have to indicate which custom message types are to be translatable – if you don’t configure this, you will run into issues as described above.

    So when creating custom posttypes with Toolset Types and you are using Polylang, after you’ve created your custom post type:

    • Go to Languages -> Settings
    • Select Settings for Custom post types and taxonomies
    • Check the checkboxes for your newly created post types and Save
    • This reply was modified 7 years, 11 months ago by tredneb.

    Please consider reopening this issue. Although you can edit all SEO titles by hand, it is quite tedious work, especially in my case where I have 9(!) languages. To fix the concatenation I have to go to each page and manually set the SEO title for each language.

    Just setting the correct SEO title for the default language does not fix this issue for me as I then still see concatenated titles for all other languages.

    Short update – the next and previous links on the Events Calendar use Ajax. Somehow any options in the URL (that is not rewritten to a permalink) get lost in the Ajax call. I disabled the Ajax call by editing one of the Events Calendar javascript source files. This was however more a hack than a structural solution (as the change will be lost at the next update of the plugin).

    Please ignore my previoius post on this subject – I’m using Events Calendar and not Events Manager.

    Script works fine, unless you needed to disable the Ajax call – which in my case I had to as the ajax call didn’t work well together with mqtranslate. Therefore I used the following (which seems to work fine in my case)

    // Changes past event views to reverse chronological order
    function tribe_past_reverse_chronological ($post_object) {
    if(tribe_is_past() ) {
    $post_object = array_reverse($post_object);
    }
    return $post_object;
    }
    add_filter('the_posts', 'tribe_past_reverse_chronological', 100);

    Any reasons why there was specific code for Ajax in the original snipet?

    I’m experiencing similar problems using mqTranslate. I added the code from the first post to my theme’s functions.php to resolve some other issues I had with translations for the events calendar.

    On the site I’m supporting I’m however still experiencing the following: if you are on a list view and select “Prevous”, the events calendar is shown in the default language whereas the rest of the site is shown in the correct language. The permalink structure you use does not make any difference, as I’ve tried multiple.

    Example:
    1. if you navigate to http://aslbislfoundation.org/nl/events/
    (make sure that the site is still in dutch, or at least not in english)
    2. select “Eerdere evenementen” (or your non-english equivalent)

    Result: You end up on the previous events page, where the URL is
    http://aslbislfoundation.org/nl/events/list/?action=tribe_list&tribe_paged=1&tribe_event_display=past
    Note that the url still indicates nl as a language, and all of the site content is still shown in dutch except for the parts of the events listing – those are shown in English (which is the default language for the site). Also to be noted: at the bottom of the page is the events widget, and this does show events with their content in Dutch.

    Example (cont.):
    3. reload the page (F5)
    Result: now all content is shown in dutch.

    Any ideas on how to resolve this via the functions.php

    (Note that I’ve also raised this issue against the developers of The Events list as it seems to be a generic issue they have when there are translations – https://ww.wp.xz.cn/support/topic/pagination-links-load-pages-in-wrong-language)

    I’m experiencing similar problems using mqTranslate – and I’ve searched the forums and there seem to be issues with all translation software (so I’m not considering switching translation modules).

    On the site I’m supporting I’m experiencing the following: if you are on a list view and select “Prevous”, the events calendar is shown in the default language whereas the rest of the site is shown in the correct language. The permalink structure you use does not make any difference, as I’ve tried multiple.

    Example:
    1. if you navigate to http://aslbislfoundation.org/nl/events/
    (make sure that the site is still in dutch, or at least not in english)
    2. select “Eerdere evenementen” (or your non-english equivalent)

    Result: You end up on the previous events page, where the URL is
    http://aslbislfoundation.org/nl/events/list/?action=tribe_list&tribe_paged=1&tribe_event_display=past
    Note that the url still indicates nl as a language, and all of the site content is still shown in dutch except for the parts of the events listing – those are shown in English (which is the default language for the site). Also to be noted: at the bottom of the page is the events widget, and this does show events with their content in Dutch.

    Example (cont.):
    3. reload the page (F5)
    Result: now all content is shown in dutch.

    Note also that I added the following code to my theme’s functions.php to resolve some other issues I had with translations for the events calendar (picked up the code from https://ww.wp.xz.cn/support/topic/mqtranslate-urls – I’ll also raise this issue on that thread)

    // hook
    
    add_action('em_event', em_qtranslate, 0, 3);
    
    // qtranslate
    
    function em_qtranslate($target, $arg1=null, $arg2=null, $arg3=null) {
    $target->event_name = em_qtranslate_string($target->event_name);
    $target->event_owner = em_qtranslate_string($target->event_owner);
    $target->post_content = em_qtranslate_string($target->post_content);
    }
    
    function em_qtranslate_string($raw_string) {
    if(function_exists('qtrans_useCurrentLanguageIfNotFoundUseDefaultLanguage'))
    $output = qtrans_useCurrentLanguageIfNotFoundUseDefaultLanguage($raw_string);
    else
    $output = __($raw_string);
    return $output;
    }
Viewing 13 replies - 1 through 13 (of 13 total)