adagiomarine

Thanks for the tips. On clicking “Rebuild Sitemap” my results are still an empty sitemap.xml file.

What I have done:

1. created empty sitemap.xml, and sitemap.xml.gz – set 777 permissions
2. temporarily set 777 permissions on my blog root at /xd1/homes/hash/41/a2141/90/05/u20590/seekerblog.com/www/
3. Disable, then enable Sitemap Generator 2.7.1
4. Click Rebuild Sitemap.

When I click Rebuild, my browser page clears all the plugin content in about a second.

Dang – any help much appreciated!

After about a week I received a very nice reply from Technorati support [see below]. They fixed the problem, though I do not know exactly what they did.

Note that she included a new [to me] type of query to verify whether your WP categories are being auto-indexed as tags.

https://www.technorati.com/tag/Military?from=https://seekerblog.com

I see that query is available under Search/Options.

Hello Steve,

Please accept my apologies for the delay in getting back to you. We’ve been experiencing a backlog in support and are
working hard to address everyone. I’ve taken a look to see if we are successfully indexing your blog. After making a small
adjustment, it looks like all is in order and your blog has been indexed with your most recent posts and tags.

https://www.technorati.com/tag/Military?from=https://seekerblog.com
https://technorati.com/search/seekerblog.com
Shows: Last updated 3 minutes ago
Tagged Climate Change, Counter Terrorism, Education, More ?
Technorati Rank: 151,285 (38 links from 19 sites)

If you do see the issue again, please contact us. Sometimes it takes a little time for the ping to reach us to alert our spiders to
index your blog. If you find it is taking a while for the index, you can ping us directly from “technorati.com/ping”.

Do not hesitate to contact us if you have any other questions. Thank you for using Technorati!

Best Regards,
Janice Myint
Customer Support Specialist
Technorati

I replied with a new problem, that WP categories were not being indexed. I also received a reply – and that now seems to be fixed also.

So I’ve shifted from unhappy to very happy with Technorati ??

Duh…Sorry for the dumb question folks – I worked out that Options/WordPress address (URI) must be set to the install directory.

Steve

Many thanx macmanx – revising .htaccess to the autogenerated rule set seems to be the fix.

I kept the short-form .htaccess in ~/test/ because my recall was that using the WP ruleset caused problems in the main blog. A helpful forum advisor suggested the rule set above.

I don’t remember what the problem was. And I don’t understand why the short-form .htaccess “fixed it”.

This time I will keep better notes ??

Steve

I unchecked the option “Attempt to notify any Weblogs linked to from the article (slows down posting.)”.

That speeded up posting dramatically – I would say it is OK now, typical post takes 2-5 seconds.

If I add a trackback URL I don’t notice any slowdown.

Dang!

I dinged Apple in my just-posted reply, then discovered that Live Preview formatting doesn’t work in IE6/PC! I have tested with both Default and Manji themes – neither displays correctly.

Of course it works perfectly in Firefox Mac/PC, sigh.

Could this be why some WP users report “no workee” and some report “OK for me”?

I also tested IE6/PC (on XP SP1) using Chris’s demo page

https://www.softius.net/wp/plugins/comment-live-preview/

which also does NOT work on my PC.

Any suggestions mucho appreciated!

This is to update and correct my 3/8 post that Live Preview did not process HTML tags. Today I finally had time to dig into this. As pointed out by fuzzy_logic the plugin works fine – it is really quite nice, many thanks to authors Jeff & Iacovos.

There’s a saying that “knowledge of existence is the key to finding stuff”, right? Knowning it would work motivated me to figure out how to make it work. It turns out my original problem was due to testing Live Preview in Safari and giving up too easily. It installed easily in my WP1.5/Manji2 theme – I didn’t try running unmodified Manji2 comments.php – I inserted the <?php live_preview(); ?> call where I wanted the preview. No other changes required.

The nice styling buttons builtin to Manji don’t work properly in Safari either – c’mon Apple get it together!

Fuzzy_logic> Do some research before you post.

Sorry if I got it wrong. I spent an hour+ testing, it never displayed any of my tags, such as simple .

And, perhaps not important to others, but it definitely doesn’t display pasted XHTML – I inferred that it was trapping keystrokes(?).

That said, I only tested on Mac OS X – maybe what I saw is platform specific?

I think this is an important issue for WP – the user community expects comment preview.

Steve

Oops, after testing this morning – I don’t think we should use the ComPreVal plugin at this stage of development. It is very nice, but has what I think is a fatal flaw that will make your commenters very unhappy.

If invalid XHTML is entered, when you select Preview button, you comment is gone!

Even if the comment was not trashed, the user is going to want to know why it did not validate.

Would a better option be to best-efforts render the XHTML – flag it as invalid, let the user try to figure out what is wrong by looking at the source and the rendered version?

While I’m piling on feature-requests, it sure would be nice if the Preview plug-in allowed for a captcha. I don’t see how to include a captcha as ComPreVal is implemented (maybe to dim to see how it could be done).

Cheers, Steve

So, is there really no basic preview plugin for WP?

The Live Comment Preview doesn’t seem to do anything I need – it doesn’t offer an HTML viewer, just plain text echo.

I’m testing ComPreVal: https://dev.d10e.net/wordpress/ recommended above. So far it looks good. Installing with Default theme was trivial. Now I’m looking at integrating with my Manji2 theme.

Steve

Macmanx, re:

https://www.ads-software.com/support/topic.php?id=26413#post-148582

that doesn’t seem relevant if I’m not totally lost. Wasn’t that problem associated with comment registration requirment? I don’t use that, was only trying to use name & email.

Steve

Macmanx wrote: “Download WP v1.5 again, and delete comments.php for the classic and default theme”.

Thanks – I executed your steps, then tested with ‘default’ theme (and also the Manji2 theme). I get the same results – given that commenter is required to enter name and email. Same as before.

BTW, it seems to me there is a disconnect between the classic, default themes and the Dashboard. The admin has the option of required name/email entry, but the comment form has no text fields for name/email.

Steve

After more testing, I’m a bit confused. By switching to Classic or Kubrick themes I eliminate customization of Manji w/ additional javascript, and am running a “stock 1.5Final”. Yet, all themes fail the same way in Safari – “Error: please fill the required fields (name, email).”

In fact the Classic or Kubrick themes don’t even have a place for user to enter name/email.

If I disable the name/email comment reqt, everything works. Which I will do until I figure this out.

Thanks, Steve

>submit button works for me when using Safari (testuser8).

Thanks heaps, mate – has to be my config. What is testuser8?

>Make sure that you have javascript enabled in Safari

Yes, can’t operate w/o javascript. I’m running latest OS, latest javascript – I’ll bet my glitch is related to additional .js added to support OmniOutliner DHTL.

Both Firefox and Safari will ‘see’ the same .js environment, but IE will not.

Steve

Macmax – does the add comment work for you on Safari/Firefox? If so, that tells me the problem must be in my config.

Theme is manji2. To see if theme-dependent, I also tested with theme=default ==> same result on Safari & Firefox.

Blog URL is https://seekerblog.com

Khaled answered my query re: Manji2 yesterday as “The buttons don’t work on mac IE, or safari. This is something I’ve tried to rectify but my mac friends haven’t found a solution. I’m told that a new version of safari is being prepped soon that should be able to deal with the javascript.”