Forum Replies Created

Viewing 5 replies - 1 through 5 (of 5 total)
  • Thread Starter biorkes

    (@biorkes)

    So I contacted my theme developer and Woocommerce.
    This is what I got from the support:
    “Ajax has not changed in 2.6, but the logic in layered nav has. So if these are using that they may need compatibility updates.”

    I don’t know if that affects the filters, but it is important information.
    Still can’t fix the Ajax Filters. I had a backup with no updated. I started updating one by one. After I updated WooCommerce, Ajax Filters went wrong and stopped displaying any kind of filters or attributes. So IMO WooCommerce updated this logic too. I don’t know…

    Thread Starter biorkes

    (@biorkes)

    Hi,

    Thanks for the advice.
    Recount Terms did not solve the problem.
    Adding new filters to the widget area does not seem to work – still the same.
    Tried to Disable/Enable the Woocommerce and the Yith Ajax Filter plugins one after another – still no success.
    I noticed that there are several users who complain of similar problem.

    Thread Starter biorkes

    (@biorkes)

    Thank you, Sir! I fixed the file names – everything is now correctly translated in the backend. I have one more question: Does this translation affect the widget data like: Month, Date, Day, Weather conditions ( clear sky, raining etc.) or this can be done only through the Openweathermap web?

    Thread Starter biorkes

    (@biorkes)

    Yes I forgot about the other 2 ..sorry mate. Here we go. I am still trying to manually add bulgarian language. It appears in the plugin section, i can select it. But some lines still are not translated also the weather widget is not translated too… I use the default theme.

    I tried to translate it, because in bulgarian language somе abbreviation are not correctly translated by wordpress. Currently my widget is translated because I had changed the wordpress default language.

    Try it now – 2 folders with the two themes:
    https://drive.google.com/folderview?id=0B5G_tSZkl6E4Mmp5NmlyeDlIYTg&usp=sharing

    Thread Starter biorkes

    (@biorkes)

    FIXED!

    Seems it was an .htaccess problem. If you have FontAwesome problem or similar issue, open .htaccess and paste this:

    <FilesMatch “\.(ttf|otf|eot|woff)$”>
    <IfModule mod_headers.c>
    Header set Access-Control-Allow-Origin “*”
    </IfModule>
    </FilesMatch>

Viewing 5 replies - 1 through 5 (of 5 total)