aljuk

They’re working fine for me.

“We just released 2.0 which works with 3.0.1. WP.org just hasn’t updated yet.”

According to the Blue Layer website, the update (as of end of June) is 1.6. According to the latest plugin update itself (as of mid August), the new version is 1.1. So what is version 2.0 ???

And as I understand it, this is no longer open source, but a commercial plugin, so correct me if I’m wrong, but WP.org won’t be hosting it.

<?php $auth = esc_attr( get_the_author() ); ?>
<a href="<?php echo get_author_posts_url( $auth ) . $auth; ?>" title="yourtitlehere"><?php the_author(); ?></a>

I installed this plugin yesterday. I came by here looking to submit a feature request, and saw this thread, and thought I’d chip in. This plugin is brilliant, I’m really impressed. Usability is awesome. I’ve got it working on a large site I’m developing with a huge plug-in count, and it’s working like a charm, no conflicts, nada. I’ve given it a thorough testing. Good work Mr. Chan.

A commercial plugin (“user self delete”), isn’t a solution.

This is a basic cms requirement, and it really should be standard in WP. In Europe, it’s a legal requirement under data protection laws.

For what it’s worth, I have a methodology that seems to be working for me:

1. added to functions.php :
remove_filter (‘the_content’, ‘wpautop’);
2. installed “tinymce advanced” plugin, and enabled “stop removing the p and br tags…”
3. use ‘br class=”blank” /’ for rare occasions when I need two br tags in a row (to prevent a paragraph closing and wrecking a float, for example)

Code stays consistent between editors.
No hacks to core files.
No validation issues.

I’ve susequently discovered that if I publish a post without setting ‘aktt_notify_twitter’ to ‘yes’ before I click publish, it gets set to ‘no’ and can’t be changed. In other words, the tweet only gets sent on the first ‘publish’ and can’t be engaged for a post that was initially published without being tweeted.

It’s too lumpy and fiddly. I run a multi-user blog, contributors are non techies, they could never get their heads around it.

I’ve just installed this for the first time. I’m just using it to display tweets, not to send them. My first test tweet took 10 hours to show up. My second test tweet I updated manually from within WP Admin. That one took 20 minutes.
Shame, this plugin looked quite promising.

I’ve now tested the previous version of the plugin, 1.0.1 – works perfectly in WP3, and validates to xhtml strict.

Hi, just regular English I’m afraid, no accents, utf-8, running on local MAMP.

I’ll check with Firebug as you suggest as soon as I get a moment, probably this evening. I will also check my other browsers and see if I can localise the behaviour, and get back to you.

Thanks.

Hi, Alphawolf.

WP 2.9.2, Firefox Mac 3.6.3

I set page title, slug etc., clicking Save for each, and the settings look like they’ve taken. All looks good, no indication of anything abnormal.

As soon as I navigate away, refresh the page, or check the regular WP fields for any of those settings (all after saving), either at the time, or later, they’ve gone. With testing further to my initial post, I can confirm that settings were NOT saving at all (100% of the time, not 50% of the time as previously stated).

Pro web designer, been building WP themes for a good few years, am positive there’s no pilot error.

Also, unrelated (?) issue – I was working on a site the other day, had the plugin installed to test it out, everything looked normal, I hadn’t touched any settings, then noticed the icons had switched from set 1 to set 2. No idea why.

It must be something my end, in my base starting theme. I’ve tried the classic and default themes and permalinks work for them fine. I’ll add comment once I work out what I’ve done or not done that’s caused this, because it appears to be a very common issue with a lot of people.

I’ve got the same thing. It’s telling me to clean out the tables in an already existing db (which doesnt actually exist). I’ve installed local dev sites using wp and mamp many times without a hitch, so I cant understand why it thinks its seeing its db. The only thing I’m doing differently with this install is putting the wp inside a folder in the site, rather than in the root. Weird, and annoying, and stressful since this is on a commercial gig.

Any advice much appreciated!

Ok, I’ve got my install working, it was pilot error.