dreamingof8a

Nevermind, found it. Stupid mistake, no plugin error.

Okay, forget what I wrote – I just realized I posted to the wrong forum – sorry!! I’m using an old version of another “newsletter” plugin …. my bad. Will have to give yours a try ??

Thanks.

But that way the address would also change with the redirect to xxx.net/gallery rather than gallery.xxx.net, right?

I had the same error showing and all I had to do was show all options in the admin area and setup th etag/category etc settings.

Thanks

Okay I guess it was easy in the end – just used the same hook wp_enqueue_scripts – that seems to do it. Thanks for pointing me in the right direction!

The original enque is inside a function, which is then call via
add_action( 'wp_enqueue_scripts', 'function').

I tried your suggestion using àfter_setup_theme` but no luck.

Do you know of any list where I can see the order of all actions? Can’t seem to find it in the codex …

@ bluff03: I believe you are looking for something like this?

@jaaaarne: true, that is still confusing me a lot! A Gallery has subalbums, not the other way around …

Have you tried to use the lang tags in description and so on? According to some older posts and an even older changelog of nextGen Gallery, the two plugins shold work together now.

Maybe you can try it out?

I’m actually waiting for confirmation of the same question as I want to switch but this issue is important for me.

See also my related posts here, here and here.

It would be great to either implement multi language into the plugin itself or at least allow the usage of language tags via polyglot or qTranslate.

Hi didier,

I am considering to use NextGEN gallery and qtranslate together for my blog – can you give me a short comment on how they work together? It seems in your case without problems?

So all I do is install both plugins and use the language tags (short or standard?) in the NGG fields I want to translate, and that’s it?

Any feedback is much appreciated!

for some reason it works now …

Okay, found the bad guy: The plugin “Kill Preview 1.0” is causing the trouble – no idea why since it has been working up to now. Anyway, don’t need it ??

Another thing came to my mind:

PHP got upgraded on my all-inkl webserve recently, it’s running v5 now instead of v4 – could this be the problem? Is there a way to find out whether there are any incompatibilities within post.php, e.g. is there a compatibility checker of some sort available?
Or could anyone help me out and go through the old post.php and tell me if there are possible problems – i don’t really know enough about php4 vs. php5 myself.

Cheers

Haven’t tried that yet because since I last used post.php I haven’t done anything to the plugins. But I will try it anyway.
Upgrading is sort of in the process, the problem is that for my theme I did some hard-coding in the wordpress core files (bad idea, I know now) so the upgrade will have to wait until my new design is ready.