Dan Jones

I know this is a bit old, but this isn’t an Instagram-specific bug. I discovered the problem with a Twitter embed that had emojis in it.

Then, to test, I tried to put just those emojis into a post, and it broke the post. Everything up to (but not including) the emojis were displayed, but the rest of the post was gone.

On the edit post page, only the post up to the emojis were shown. I then checked the database, and it was the same. Everything up until the emojis were saved.

For testing, the emojis I used were ????.

Not what MIT says, what the Free Software Foundation says, and that’s linked straight from the plugin guidelines page.

It says “compatible with” GPLv2. According to GNU, the MIT license (they call it the Expat License) is compatible.

1) Can you use one-click upgrades without entering any etxra data? That is, do you just click the button and go?

Yes

2) Do you have disallow_file_mods or anything similar set in your wp-config.php?

No

3) Do you ever have to enter a username and password for FTP to upgrade?

No

Seems that it should work just fine.

I figured out how to fix it, but I don’t know if it would break other things.

In wsl.authentication.php, if I comment out the code:

if( get_option( 'wsl_settings_redirect_url' ) != site_url() ){
                $redirect_to = get_option( 'wsl_settings_redirect_url' );
}

it works for me.

With a little more testing, I’ve figured out that the problem actually occurs on any login, but only if logging in from the comment section. If I log in via the main login page, it always redirects back to the homepage, as I would expect.

So you know, the same problem occurs with Google.

I’m guessing any that require a callback URI will have this problem.

If I can find the time, I’ll have a look at it. I know the WP Super Cache plugin has a “Domain Mapping” feature to make it work with Multisites that use Domain Mapping, so maybe I can use some of that code to get WSL Twitter login to work. There’s got to be some trickery with the callback URL, or something.

But to be honest, I doubt I’ll find the time. It’s just not that important to me. It would be nice to have, but unless I can justify it as something important for work (which maybe I can), I doubt I’ll be able to get around to looking at it.

Never mind. I figured it out. Apparently I was supposed to put a bunch of code in the template. I just reset it to “white.” I assumed that was for extra stuff.

It’s completely unintuitive.

I’m having similar problems to those described above. I’m using WordPress 3.5 (just upgraded today).

It seems to work fine on posts (haven’t tried pages), but isn’t working properly for categories/tags. When I try to add a new widget to a category (after selecting “Customize” in the “Category Widgets” settings), after I save the category, and go back to the Category page, my new widgets aren’t found.

I can remove widgets, however.

I just had your first problem after upgrading to 2.8.3 on one of my blogs. I just reinstalled a new copy on top of the old, and it got rid of the problem. I figure something screwed up with the download.

By the way, I finally figured out a way to do this. My contact form is on a Page, so I created a custom page template in my theme.

Before The Loop, I put in:

<?php if (is_user_logged_in()) : ?>

And then after The Loop, there’s:

<?php else: ?>
<!-- Message telling them to log in -->
<?php endif; ?>

Then I just used that custom template for that Page.

I was wondering the same thing. Has anyone figured this out yet?