jaseone

I also had issues with my tweets not updating using b3 (and previously b2) when it worked fine except for the whole 3 weeks ago thing with b1. aktt_notify_twitter was set to 0 so I was a little stumped then on a whim I decided to check to see if my password was right and it wasn’t. Correcting it allowed the updates to take place.

So I’m guessing b1 just used the ID but the more recent betas uses the username and password? Maybe it uses them if the password is supplied otherwise it just uses the ID? I guess I could look at the code to see what it is doing but I’m lazy.

I wouldn’t mind it if it was signing up to get an API key just for Akismet but currently you need to create a whole WordPress.com blog, which is exactly what people installing WP don’t want as most people installing WP are those trying to escape free or paid hosted services.

Plus I have heard of a lot of false negatives with Akismet and SK2 is yet to do that for me, nor has it had a single false positive, so why should I use Akismet again?

Yes, but would you go so far as to state that WordPress is supported software? Supported software to me would involve being able to raise a ticket stating my problem and then have it resolved via support staff, kinda like the way a web host’s system works.

We all provide support when we can but there are many issues that go un-addressed, which is understandable given the situation but if WordPress was “supported” then every single one of those issues would be addressed in some way.

I would very much prefer it if the attitude was more that issues with development releases can’t be discussed in the main forums but can be discussed in this forum, leave the “not supported” bit out of it.

Yes.... maybe need another post somewhere about THIS IS BETA SOFTWARE; USE AT OWN PERIL; and we don't actually "support" it since it's not release quality yet?

Isn’t it the point of this forum to discuss issues with the beta?

I agree there should be warnings posted about the dangers of using the beta but just state that any issues should be discussed in this forum until 2.0 is released, don’t add anything about it not being supported as stable WordPress itself isn’t even supported.

Imagine that, a beta theme not tested or developed to work with a beta release of WP not working. Who woulda thunk it?

Was that really necessary? This is the place to discuss issues with 2.0 beta is it not?

Okay on a whim I tried the other method in the Codex:

function keywords_createRewriteRules($rewrite) {
global $wp_rewrite;

// add rewrite tokens
$keytag_token = '%tags%';
$wp_rewrite->add_rewrite_tag($keytag_token, '(.+)', 'tag=');

$keywords_structure = $wp_rewrite->root . "tags/$keytag_token";
$keywords_rewrite = $wp_rewrite->generate_rewrite_rules($keywords_structure);

return ( $rewrite + $keywords_rewrite );
}
add_filter('search_rewrite_rules', 'keywords_createRewriteRules');

That works as long as I ALSO have the below in my .htaccess:

RewriteRule ^tags/?(.*)$ /index.php?tag=$1 [NC,L]

One will not work without the other, what is up with that?

Okay I officially give up…

I have tried using WP’s internal rewrite rules and .htaccess but in no way can I get this to work:

/tags/tagname –> /index.php?tag=tagname

Trying to do it in .htaccess with:

RewriteRule ^tags/?(.*)$ /index.php?tag=$1 [NC,L]

Just results in a 404 and using WP’s internal rewrite rules I can’t for the life of me set a GET variable.

So how can you do this?

What I currently have:

function taggerati_rewrite($wp_rewrite) {
$taggerati_rules = array(
'tags/(.+)' => '/index.php?page_id=271&tag='.ltrim($_SERVER['REQUEST_URI'],"/tags/")
);
$wp_rewrite->rules = $taggerati_rules + $wp_rewrite->rules;
}
// Hook in.
add_filter('generate_rewrite_rules', 'taggerati_rewrite');

That gets me as far as rewriting /tags/anything to ?page_id=271 but the second GET parameter never seems to be applied even if I hardcode it to one of my tags so it doesn’t load the specific tag page just the generic tags page, what am I doing wrong?

Ryan,

How would you use WP’s internal rewrite structure to rewrite:

tags/tagname

into:

index?page_id=271&tag=tagname

Where tagname could be anything.

I played a bit with it trying to follow your example but haven’t been able to get quite there, can you do it with internal wordpress functions or should I just parse the requested URL to grab it?

Have you seen https://codex.www.remarpro.com ?

If you aren’t using them in your CSS or within links then I can’t see why not.

The only search plugin I know of is: https://www.semiologic.com/projects/search-reloaded/ but I don’t think any current plugins will go so far as searching linked files so you would be looking at something custom built to achive that.

That’s the BAStats plugin, I’d disable it and then check with the plugin author for a fix.

How large of an article? Can you paste the text of the post anywhere?

To display photos in your sidebar, see here