Viewing 15 replies - 1 through 15 (of 19 total)
  • webconsole throws this error, maybe it helps.

    downloadable font: download failed (font-family: “FontAwesome” style:normal weight:normal stretch:normal src index:1): bad URI or cross-site access not allowed
    source: http://domain.nl/http://domain.nl/test/?ngg_serve_fontawesome_woff=1?v=4.0.3 test
    downloadable font: download failed (font-family: “FontAwesome” style:normal weight:normal stretch:normal src index:2): bad URI or cross-site access not allowed
    source: http://domain.nl/fonts/fontawesome-webfont.ttf?v=4.0.3

    Plugin Author photocrati

    (@photocrati)

    @ivdbroek – My first thoughts are this may be server environment related, what details are shown under Gallery > Overview?

    – Cais.

    Plugin Author photocrati

    (@photocrati)

    @ivdbroek – Those settings seem like they should be fine, have you checked with your web host to see if there are any restrictions that may be in place that would see FontAwesome as a potential “cross-site access” issue?

    – Cais.

    Besides adding mime types (which didnt help) they see no issues.
    the ngg addon code does use different urls:

    @font-face{
      font-family:'FontAwesome';
      src:url('../fonts/fontawesome-webfont.eot?v=4.0.3');
      src:
      url('../fonts/fontawesome-webfont.eot?#iefix&v=4.0.3')
          format('embedded-opentype'),
      url('../http://devalkeniers.nl/test/?ngg_serve_fontawesome_woff=1?v=4.0.3')
          format('woff'),
      url('../fonts/fontawesome-webfont.ttf?v=4.0.3')
          format('truetype'),
      url('../fonts/fontawesome-webfont.svg?v=4.0.3#fontawesomeregular')
          format('svg');

    source: http://devalkeniers.nl/test/?ngg_serve_fontawesome_css=1&ver=3.8.1

    Plugin Author photocrati

    (@photocrati)

    @ivdbroek – This is what appears in our implementation:
    url('../fonts/fontawesome-webfont.woff?v=4.0.3') format('woff')
    … where you are showing the full domain path being included above. I would think that needs to be sorted out.

    – Cais.

    how do i solve this, since i did not alter the code in any way.
    I do have been looking around for the file to do some trial and error. but couldnt find it

    Plugin Author photocrati

    (@photocrati)

    @ivdbroek – If your theme is also using FontAwesome you may be able to temporarily work-around this issue by finding and commenting out its implementation.

    I would suggest similar for NextGEN Gallery but that may be much more complicated.

    Have you contacted your theme author to see if they have any suggestions?

    – Cais.

    yes i did at first, they said to go to you. so this is gonna be a vicious circle 😉

    Could u point me towards disabling Fontawesome in NGG?
    Then ill contact Themeowner how i can disable it in them.

    Ill go then for the easiest way 😉 (my preference is disabling it in NGG though)

    Plugin Author photocrati

    (@photocrati)

    @ivdbroek – I stopped counting at 15 different instances that would have to be reviewed if disabled / commented out.

    Feel free to open the plugin in a good IDE and search for “fontawesome” … we generally only enqueue it when needed but to be safe every instance should be reviewed before it is changed. This would also be over-written with the next update of the plugin which I would imagine will be a lot sooner than what your theme author is even considering so you would need to do all of the work over again if this particular conflict does not get sorted out.

    – Cais.

    Apparently the probems is in server FA for IIS servers
    I out commented 1 line and it fixed the problem 🙂

    // Font Awesome
                if (wp_style_is('fontawesome', 'registered')) {
                    wp_enqueue_style('fontawesome');
                }
                elseif (strpos(strtolower($_SERVER['SERVER_SOFTWARE']), 'microsoft-iis') !== FALSE) {
    //              wp_enqueue_style('fontawesome', site_url('/?ngg_serve_fontawesome_css=1'));
                }
                else {
                    $router = C_Component_Registry::get_instance()->get_utility('I_Router');
                    wp_enqueue_style('fontawesome', $router->get_static_url('photocrati-nextgen_gallery_display#fontawesome/font-awesome.css'));
                }

    source: module.nextgen_gallery_display.php

    Plugin Author photocrati

    (@photocrati)

    @ivdbroek – Thanks for the follow-up and your work-around. Please remember to check for this in future releases as you may need to re-modify this file for your installation.

    – Cais.

    Thanks for the help and hope the code will get reviewed, since clearly it is not working as supposed.

    Plugin Author photocrati

    (@photocrati)

    @ivdbroek – Thanks. I have added this topic to our internal notes related to FontAwesome so our developers can add it to their review.

    ~Cais.

    I have the same Problem on IIS on Windows Azure

    WordPress 3.8.3
    Photocrati NextGEN version 2.0.65, Photocrati NextGEN Pro version 1.0.17
    Site: http://www.bestspotsintheworld.com/fraser-island/

    I could not find the module.nextgen_gallery_display.php

    Thanks for your any suggestions.

    Daniel

Viewing 15 replies - 1 through 15 (of 19 total)
  • The topic ‘Breaking icons’ is closed to new replies.