gab.ro

I haven’t brought this up on the forum for Jetpack yet. Right now I’m happy I have everything working and don’t really feel like putting more energy into it. Maybe later.

I’ve done a bit more research, the memory limit could be an issue. If I get similar problems again, I will look into it some more.

Thanks for your help, Rob!

OK. I’m getting closer and closer to the source of this problem.

Short story:

I’ve come to realize that Jetpack is the main troublemaker so you can consider the problem closed, from your perspective. But if you still want to take a look at this oddity, you’re most welcome.

Long story:

After the last upgrade, Jetpack started to cause the white screen of death in the plugins page even without your plugin being activated.

After extensive testing, I’ve noticed that when your plugin was activated some of the Jetpack components cause the white screen of death allover the wp-admin section, while others only caused it in the plugins section, while two of them were causing no problems at all.

Since the ones that cause no problems are the ones that I need most (Contact Form and Enhanced Distribution) I will consider the problem solved.

Just for posterity, I will also repeat that this problem is only present when English is NOT the language of the site.

Odd, I know, but this is the behavior that I get.

Allright. I made an admin account for the new address as well. You probably have the randomly generated password in your inbox (or spam directory).

OK. I just made an admin account for that e-mail address and you have probably received a randomly generated password.

The site is intranzitie.org

Hey!

Did you also try it with Jetpack and with any other language than English? Remember that’s the only case that I’m getting the problem.

I don’t know the email address of pro (a) tri.be

On the contact page if your website, I only found a contact form: https://tri.be/about/contact/

Is it all right if I use that?

Regards,
Gab

Thanks mate! Can’t wait for the results!

Hey roblagatta,

I have done some huge progress today in fixing this.

I deactivated all other plugins and activated the default theme.

I messed up all the theme settings in the process, but at least I have found the culprit: it is WordPress Jetpack!

The problem with The Events Calendar appears only when WordPress Jetpack is activated + connected to WordPress.com. If it is only activated but not connected to WordPress.com, there is no problem with The Events Calendar.

I have no idea how to use pro a/ tri.be for sending admin creds. I would gladly also send FTP data, if you think it would help. But with this new information (jetpack) perhaps you will be able to recreate the problem locally.

Thanks,
Gab

Thank you, I sure hope this gets fixed. I can confirm that the problem is still present for plugin version 2.0.8, under WordPress 3.4.1.

Hey! Thanks for your reply!

I’m not using any plugins for multilingual support.

I’m simply changing the language like you do in wp-config.php

The only difference is that when a network of sites is used (WPMU), you get that option as a drop-down under Settings -> General.

That’s all I’m doing…

OK, I also tested it without any Romanian po/mo files and it behaves just the same:

If the selected language is English, everything is aOK, but if the selected language is Romanian, the front-end is OK, but the back-end shows the white screen of death.

You might wonder why I’m selecting the Romanian language if I have no Romanian po/mo files for your plugin. It’s because I need translating for WordPress, and the theme and other things. For the plugins where there are no Romanian po/mo files, the default (English) strings should be displayed. And I’m getting this behavior with all other plugins except for the-events-calendar.

The site where this is happening is https://intranzitie.org/

It’s public and “in production” (so to speak) so the inability to use your plugin is causing me hardship…

Yeah, I created new po/mo files. And selected the language from the backend (since it’s a multi-site installation).

I’m also experiencing this. It’s a bug, I think.

In the future, you can also visit the plugin website for similar questions ??

Hello

You want your nano to behave differently when you’re in the admin section than when you’re viewing the site. What you need is the conditional tag is_admin:

if(!is_admin()){
  return 'post_title';
}
else{
  return $orderby;
}

Notice the $orderby argument. In order to be able to use it, put it in the Hook Arguments field. That is the default value, so the nano does not modify it when you’re in the admin section.

Regards,
Gab

It’s not very nice of you to not respond. One might say it’s even rude. It’s been 4 days.

I’m assuming that either you solved the problem or that it doesn’t need solving anymore and calling the topic resolved.