Forum Replies Created

Viewing 15 replies - 46 through 60 (of 62 total)
  • Thread Starter alarch

    (@alarch)

    One other thing – the javascript causes a conflict with another plugin (which I’ve been forced to disable). This problem wasn’t there with the previous version of FA Lite.

    Thread Starter alarch

    (@alarch)

    Yes, Preload images is checked. Another website with the same problem: http://www.forestschoolwales.org.uk

    The problem is very erratic though, sometimes occurring, sometimes not – which is very strange. When I try and inspect the code it rectifies itself – which is frustrating. I have a poor internet connection (2Mbps max) – could this be a factor?

    Forum: Alpha/Beta/RC
    In reply to: IE can’t open blog

    I’m having a problem – my website freezes in IE6 – or takes a very very long time to load. I wasn’t having this problem leading up to going live – but typically now that the site has gone live this problem exists. the problem is in IE6 only. I’ve tried disabling all plugins – and the problem persists. I’ve recently upgraded to version 2.8.4 from 2.7 – could this be the cause? The code validates. Have a look at forestschoolwales.org.uk.

    If I disable “Run ActiveX controls and plugins” things work fine – after clicking Ok when I get the prompt “Your current security settings prohibit running ActiveX controls…”

    Yes, this would be great. I have a client who has this requirement.

    Same here, same WordPress version

    Forum: Plugins
    In reply to: using wp-sentry on pages

    Hi Pete

    Is a solution to the issue of

    making wp_list_pages (and the other internal wp functions) respect and show private posts/pages

    imminent? Is this an issue that is being addressed at core level – or are you having to deal with this through your plugin?

    Much appreciation for the work you’ve done.

    Wyn James

    That was very helpful and helped me to display language-appropriate captions on Creative Clans slideshows (one English, one Welsh) using (for the English version of the slideshow):

    ( !is_home() && (function_exists('qtrans_getLanguage') && qtrans_getLanguage()=="en"))

    The !is_home prevents the slideshow displaying on the home page.

    Thread Starter alarch

    (@alarch)

    Thanks – the ticket you mention is very useful.

    A temporary fix until this issue is addressed properly involves amending line 2168 (within get_pages() function) in version 2.7 WordPress wp-includes/post.php to:

    $query = "SELECT * FROM $wpdb->posts $join WHERE (post_type = 'page' AND (post_status = 'publish' OR post_status = 'private')) $where ";

    However, although this does the job of displaying private posts in the drop-down list of parent pages, there may be unwanted effects elsewhere. get_pages() is called in four places:

    http://lab.yukei.net/wp-trunk/nav.html?wp-includes/post-template.php.source.html

    get_pages() is also called by wp_list_pages for instance (in post.php also). So, you may end up with private pages displaying to all comers in your menu bar or Pages widget.

    So, discretion is the order of the day I think.

    Thread Starter alarch

    (@alarch)

    I haven’t the time at the moment to post a detailed explanation of what I did to get around this problem. However, I didn’t get any joy by blitzing URLs with convertURL. Instead I used Wp-highslide (along with Nextgen gallery and highslide itself) to get around the problem. There’s a fair bit of customization of wp-highslide involved to get it to work right – but I managed to get image captions to show in the correct language as well as the highslide controls. If I get the time I’ll give a detailed explanation of what I did at some point.

    Thread Starter alarch

    (@alarch)

    Using [imagebrowser id=3 template=qtrans] activates the template imagebrowser – but I can’t put this code in my gallery page otherwise I get the thumbnails and imagebrowser together. I only want the imagebrowser to open once a thumbnail has been clicked. Where then do I put the above code – because there is no user-generated page that I can insert this code into.

    Typical – I find the answer straight away after posting. The answer is to use quicktags (e.g. [:en] no closing tag) around the image descriptions and alttext in the Manage Gallery admin area. I’d still like to know why the full tags: <!–:xx–><!–:–> don’t work.

    I have upgraded to the latest versions of NextGen qTranslate and WordPress and Gettext doesn’t appear to work in NextGen gallery. I’ve followed the template approach (created a gallery-qtrans.php in nggallery folder within my active theme folder) – and used the _e() and __() functions wrapped around my image descriptions and alttext. On pre 1 releases of NextGen this approach worked fine, but now these functions don’t work at all. Has anyone got Gettext to work with NextGen and qTranslate (or other language switching plugin)?

    I have tried using the old style lang tags: [lang_xx][/lang_xx] and the new style ones: <!–:xx–><!–:–> . Neither work.

    I have a solution which seems to work well – and involves minor changes to the nggallery.php and nggfunction.php files (and also cloning, then modifying the thickbox-pack.js file for your locale). You also need to apply language tags to the “Gallery Settings” individual image descriptions and “Alt & Title Text”.

    Alex – if you read this, can you please let me know how I can contact you direct, so that you can assess my suggested changes?

    I’ve made some progress, with the admin interface now being translated and the [Show Picture List] and [Show as Slideshow] links displayed above galleries now showing up in the correct language. I achieved this in the by accessing the Gallery>Options>Gallery admin page and using [lang_xx][/lang_xx] tags around the two text entries to the right of Integrate slideshow:

    [lang_en][Show as Slideshow][/lang_en][lang_cy][Dangoser fel sioe Lluniau][/lang_cy] and [lang_en][Show Picture List][/lang_en][lang_cy][Dangoser Rhestr Lluniau][/lang_cy]

    Outstanding issues:
    When you click on the above link it always displays the relevant page in the default language – rather than sticking to the previous selected language.

    The “Next” “Prev” literals etc. displayed when you click on an image are still only in English.

    Any thoughts on these issues?

    I’ve posted on the subject of multilingual blogs/websites using NextGen before, without resolution. It’s frustrating because NextGen is an excellent plugin, and much of the internationalization work has been done on it, unlike many plugins. However, when I use it with qTranslate I only get English text. I have even failed to get it to work monolingually in the language of my choice – setting WPLANG to de_DE and with the corresponding nggallery-de_DE.mo file present in the NextGen lang folder.

    Other plugins work well with qTranslate out of the box (e.g. Advanced Search Lite) – but I have no idea why they do and NextGen does not. I don’t have the skills to make this work so I (and clearly others) are in your hands Alex. Because most Welsh websites are bilingual (typical I imagine for minority languages) compatibility between qTranslate and NextGen is crucial.

    For what it’s worth, if you can get NextGen to work with qTranslate I’ll translate the nextgen pot file into Welsh.

Viewing 15 replies - 46 through 60 (of 62 total)