fouriertransform

Well, now I feel even stupider than I did before. Hovering over the name of the redirect shows the old path in the status bar, exactly as you’d expect from hovering over a normal link, but today, actually clicking on the link opens a little dialogue with all the editable details in. I guess yesterday I must have had some kind of javascript error, so that when I clicked the link the script didn’t open the details and just went to the old link instead.

Case closed.

Additionally, the image browser and carousel features don’t work on Pods pages because NextGEN doesn’t understand which page we’re on.

Let’s say my Pod page has a URL of mydomain.com/food/fruit
Wordpress is installed in root, and the /food/fruit part is the Pod page slug.

I have a NextGEN gallery on the fruit page. I would expect, from having seen it in action, links on the image browser and carousel would go to:
mydomain.com/food/fruit/nggallery/image/apple#1 etc.

But they don’t – they link to mydomain.com/nggallery/post//image/apple#1 etc. which obviously doesn’t exist.

What’s going on, and why can’t NextGEN see the page we’re on? Can’t I make use a relative path, rather than an absolute one?

As a sanity check, I have the following code, and yes, it’s before the loop (note that as mentioned above, everything works fine when the template is page2.php):

echo get_page_template().'<br/>'; 

if (is_page_template('page.php')) {
echo 'this is page.php';
 }
 else {
echo 'this is definitely NOT page.php';
}

When viewing a page that uses page.php, I get the following output:

[theme path]/page.php
this is definitely NOT page.php

I mean… what?

I increased my memory limit to 64MB and upgraded to WP3.1.2. I still can’t insert a gallery, album or image via the visual editor, and the health check still tells me my theme in incompatible, I have a plugin conflict and I am missing calls to wp_head & wp_footer, even though I’m testing this with a clean, new default TwentyTen theme and no other plugins. And I can see the calls to wp_head and wp_footer in the header and footer – I know they’re there, I can see them!

wpdev/?callback=json&method=version gives me version 1.7.4.

I installed NGG1.7.4 on a different server, using the same hosting company (and so with exactly the same server config), and with WP3.0.1, and NGG works perfectly. The only difference between the two servers is the WordPress version. It works with 3.0.1, but doesn’t work with 3.1.2.

I give up.

My admin error log is full of the following line:

PHP Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 9088 bytes) in /home/*****/public_html/wp-content/plugins/nextgen-gallery/admin/ajax.php on line 403

which is line 403?

I have a standard installation, yes.

Incidentally, I found the ‘missing the call to’ fail messages in admin/ajax.php – it should read ‘missing the call to wp_head’ and ‘missing the call to wp_footer’, but because you have the wp_head and wp_footer wrapped in php tags, those words don’t show up during output, leading to a confusing error message.

3. Theme compatibility failed. ‘Missing the call to’. The call to what? I’m using a custom theme based on TwentyTen. All functional parts of the theme are intact – I have the wp_head and wp_footer in exactly where they should be.

In fact, I just switched to TwentyTen 1.2 – the untouched default theme that comes with WP3.1.1, and I still get a theme compatibility error.

So: with all plugins deactivated except NGG, and with the default TwentyTen theme, NGG tells me there’s a plugin/theme conflict and that the theme is incompatible.

Hello Alex, thanks for responding,

The health check failed:
1. Plugin/theme conflict failed, despite the fact that NGG was the only plugin running – all others were disabled, and all custom code in the header was commented out.
2. Image test was fine
3. Theme compatibility failed. ‘Missing the call to’. The call to what? I’m using a custom theme based on TwentyTen. All functional parts of the theme are intact – I have the wp_head and wp_footer in exactly where they should be.

It would be helpful to know what tests #1 and #3 are actually checking for – all I know is that there’s some sort of conflict, but I don’t know what with, and I don’t know how it’s conflicting. What is the test for, exactly? If I knew what was being tested I might be able to do something about it. But even when all other plugins are disabled I’m still getting a conflict.

Thanks again.

Same problem here – WP 3.1.1, NGG 1.7.4, PHP 5.2. This is really frustrating, because in all other ways NGG is the answer to my problems, but it’s next-to-useless to use on a client site when they’re unable to add their own galleries to pages.

Clicking the drop-down menu on the add-a-gallery pop-up results in an infinite spinning timer, and nothing else happens. If I manually type a gallery name into the space where the drop-down menu is, and press INSERT, the pop-up disappears and the page remains empty, but in my browser error console I get the following:

The ‘charCode’ property of a keydown even should not be used. The value is meaningless
…admin-ajax.php?action=ngg_tinymce&ver=3393a200

does that mean anything to anyone?

Good point – it’s https://www.helfagelf.co.uk/. The NEWS page is the offending posts page.

I had wanted to upgrade the WP install, but the site is live and in the middle of an important application process at the moment, so didn’t want to risk anything even worse happening.

Ok, someone’s messing with my head today. Three hours after the theme editor went missing, at literally the worst possible time, it’s back. And I haven’t made any changes that could have caused that to happen. This is fantastic news on the one hand, because now everything works again, but I hate not knowing why. And what to do about it if it happened again.

This has just happened to me, half an hour before a site I was developing was due to go live. I have no idea why it’s suddenly happened, and it’s causing me a whole world of stress, because I can no longer make small, quick adjustments to the site, I have to edit the theme files offline and then FTP them, which is crazy.

Did you ever fix the issue, egjweb? Pasting the full path to the files doesn’t even work, even though I know they’re there, I can see them!

I’m on WP 3.0.1
Plugins:
qTranslate 2.5.9
cforms 11.5
Pods CMS 1.9.3

even with all of these disabled, I still can’t access the theme editor.

Me too. Really frustrating – I’m sick and tired of seeing search results for this that only say one of two things:

1) Overwrite http.php! I did, and nothing happened
2) You’ve run out of space! No I haven’t, it’s a clean new install on a new server. And it’s happening on my other sites, too.

And I can’t upgrade to 3.0 because some of the plugins that are crucial to the site working aren’t compatible with 3.0 yet.

I can upgrade manually, but it’s really inefficient and time-consuming – especially with so many sites, so many different plugins, and so many updates to each plugin.

That is beautiful – and lightning fast! I have a lot to learn…

Thank you so much ??

Yes, it would, on reflection, because the new changes in the header are overruling the stylesheet. Even though it works, it’s bad form (and pointless and inefficient) to have conflicting values. I forgot about the stylesheet, I’m sorry! I was a little bit too hasty to answer…heh.
So yeah, probably best change the header back to how it was, removing the style=”…” bits, and just plug the new position values into the stylesheet, as I mention in the post above. Apologies for the confusion.