Forum Replies Created

Viewing 15 replies - 16 through 30 (of 73 total)
  • Thread Starter giangel84

    (@giangel84)

    Hello @inputwp my name’s Gianluca. 🙂

    Thank you for the quick reply, I wish you all the best in your work.

    I had the same issue, this is my fix:

    jQuery slug is changed from WP 5.6 version (previously slug was: “jquery”, new slug is “jquery-core”.
    On some custom themes this behaviour need to be changed to load jquery custom version with the new “jquery-core” slug across wp_enqueue_script declaration, usually inside “functions.php” and moreover jQuery needs to be loaded to the header instead of the footer.

    So, after changed the slug and the position properly, the issue is fixed.

    example:

    
    wp_deregister_script( 'jquery-core' );
    
    $footer = true;
    $header = false;
    wp_enqueue_script( 'jquery-core', MY_THEME_PATH . '/js/jquery-3.5.1.min.js', false, "3.5.1", $header );
    • This reply was modified 3 years, 1 month ago by giangel84.

    Having same issue, loading images result empty with the “default” camera image.
    Just tried to reset all and reconnect profile/token/feed with no success.

    @mrroundhill unfortunately the solution I found above doesn’t work properly.
    New theme is recognised correctly by plugin, I can save it and also the custom-theme.css is loaded, but the default theme still also loaded and that’s overwriting the custom css rules.

    How can i fix this behaviour?
    Thanks in advance.

    @mrroundhill is there any chance to make a custom theme working externally? By putting files inside the ‘/wp-content/themes/mythemefolder’, or ‘/wp-content/she_themes’?

    Just to avoid overwriting behaviour after the plugin is upgraded.

    EDIT: I found the answer by searching through the forum. 😀
    https://alex.blog/wordpress-plugins/syntaxhighlighter/adding-a-new-theme/

    • This reply was modified 3 years, 6 months ago by giangel84.

    @donnapep it would be very useful to implement a filter which make me able to set a default language code, so every time I need for a block, it’s already set with the proper choice checked. 🙂

    @andrewmrobbins There are also some strings which never translated.

    For example, in front-end single-product display: Quantity and Size, still always in english. Also in cart view Only %s left! string, never change.

    Just tried to sets an existing translation (for example ‘French’) and the problem still the same.

    Please check this issue, I bought the pro-version, and I haven’t any option to change the strings. I have to write some jQuery rows to manually overwrite the strings (bad practice).

    Another translating issue is: the subtotal in cart view, always set ‘0,00 USD’ even if the setting is set to show symbol; it get the EUR symbol properly ONLY if the subtotal is > zero, but that’s could be a bad UX for many users.
    Thanks in advance.

    • This reply was modified 3 years, 9 months ago by giangel84.

    Hi @andrewmrobbins ,

    In my case define 'WPLANG' constant, doesn’t change the language.
    Only setting the website language in wp-admin/options-general.php perform the changes.

    So, if I put define ('WPLANG', 'fr_FR'); this doesn’t work. But if I change the language to “French” from the wp-admin/options-general.php page, the plugin will translated.

    Now my issue still the same: I open the wpshopify.pot file, make the new translation files called 'wpshopify-it_IT.po' and 'wpshopify-it_IT.mo', by translating to Italian language the most part of front-end strings, then I put the files inside /wp-shopify-pro/languages, sets the website language to Italian, but the front-end strings still in English.

    I make a copy of the original 'wpshopify-fr_FR-wpshopify-public.json', by edit some strings, and saved as new 'wpshopify-it_IT-wpshopify-public.json'. Put the file inside /wp-shopify-pro/languages folder, and it works!

    So I understand that I need to make also the Json files, but I don’t know how!
    That’s because the .pot contains all the strings than Json files, which are distinct in: admin, blocks, public, wizard.

    Moreover: putting the files inside /wp-content/languages/plugins folder, doesn’t work! That means I need to reload my custom translation’s files everytime I will update the plugin.
    That’s not very understandable way to respect the standard way of WP translations.

    I have the same issue. Inside plugin’s “languages” folder there are lot of .po and .mo files but putting files inside it doesn’t work. There are also some json files and there’s no documentation about. I wrote to their Slack group but without response yet.

    I link my question to this one: How can I translate the plugin?
    Thanks.

    • This reply was modified 3 years, 9 months ago by giangel84.
    Thread Starter giangel84

    (@giangel84)

    @augustjohnston Please try to download and install the new “0.3” version of plugin ‘all-in-one-event-calendar-extended-views-fix’ from github.

    It work in a smarter way and it seem to solve the “expired link” issue.
    Any feedback would be appreciate.
    Thank you.

    • This reply was modified 4 years, 2 months ago by giangel84.
    Thread Starter giangel84

    (@giangel84)

    @augustjohnston UPDATE:
    I’m working on “the link you are following has expired” error by following these steps:

    1. Update the “AIO Event Calendar” plugin to the 2.6.1 version.
    2. Download the plugin “all-in-one-event-calendar-extended-views-fix” from this link.
    3. Remove the fix from your functions.php
    4. Install the fix plugin, but keep it disabled.
    5. Check the AIO Event Calendar and the Extended View add-on are both enabled.
    6. Go to “AIO Event Calendar” settings, click the label “add-ons” and click on “save settings”. After this, a warning message say the “extended view” add-on has been disabled.
    7. Go to “Plugins” and enable the fix.
    8. Try again to update an event.

    Now will work fine, but after a couple of minutes, the issue come back again.
    It’s not a cron function, just checked for it.
    If you redo just the steps 6 and 8, the issue disappear and then come back again.

    I will investigate more for this strange behaviour.

    • This reply was modified 4 years, 2 months ago by giangel84.
    Thread Starter giangel84

    (@giangel84)

    @augustjohnston I just updated the plugin to the lastest version (2.6.1) and it seems my account now is properly signed in to the time.ly service.
    So time.ly fixed this issue and now the extended views doesn’t get deactivate anymore.
    I deleted my fix but the “expired link” error still, while updating an event.
    I tried with the previous version of the plugin but it does the same thing.

    So, is not my fix that break the update process! It seems an plugin issue. 🙁
    However by clicking on “try again” link, the post will update properly.

    Try yourself. Update the plugin (perform a backup before), delete my fix and you can get the same problem as well.

    Time.ly use a strange way to check the accounts and the add-ons. I think that some goes wrong while this check runs, and it break the user session. :-/

    Thread Starter giangel84

    (@giangel84)

    Which version of the plugin are you using now?

    This fix is working for sure with the 2.5.44

    Thread Starter giangel84

    (@giangel84)

    Hi @giuse sorry for my typing error, obviously I meant 5.3.2 (not 3.5.2 😂).

    Now I managed to find your plugin on the result’s list with my wp installation! Thanks.

    Thread Starter giangel84

    (@giangel84)

    Hi @kinsella55 can you explain better how do you mean with “Max Mega Menu CRASHES”?

    Which kind of crash happens? Have you some errors printed to the screen or it’s just a plugin deactivation? Please read the error_logs files and give us more informations about.

    Thank you.

Viewing 15 replies - 16 through 30 (of 73 total)