kelly64

I actually ‘solved’ my problem. The issue is that OceanWP is reactive and was ‘turning off’ the sidebars based on slightly different browser settings. E.g.: my Safari browser view was ‘zoomed in’ slightly compared to my Chrome browser, increasing the size of page elements and triggering the sidebars to be disabled.

Disabling elements like sidebars to keep the main content readable is perfectly normal and reasonable behaviour for a reactive UI. But I was ignorant of the fact that it would be triggered in quite the way it was and quite so ‘easily’. Several of my site users complained of the same thing: apparently a lot of them are using laptops with less screen real estate.

Thank you very much for testing this out from your end. I’m now looking into how to tune the behaviour but, as I have purchased a license now, I’m going through the ticketing process.

I voted in the list (although my new option didn’t appear after I voted). That said, I’m assuming from your reply that there is currently no way to recursively import a directory structure as albums along with all enclosed images?

That means I have to manually import about 100 folders and about 2000 images they contain. Ouch. Migrating from the old Gallery2 is starting to look far more painful than I expected.

Upon further examination of the WordPress behavior, it is filtering/parsing ASCII newlines sent via the API into <BR /> tags. I think I sort of see your point, Otto: basically, WordPress is treating content received via the API as if it were identical to content *typed* in via the WordPress editor. What it *should* be doing it treating content via the API as raw HTML- the same as using the WordPress editor and clicking on the “HTML view” icon. At least when the API attribute “mt_convert_breaks” is set to false/no value.

I wouldn’t want to alter the behavior of the WordPress editor UI, but Wwitespace such as newlines should be ignored by the API. If this behavior is deep within the WordPress code, then I guess it needs to be fixed by “experts”.

Otto, I’m looking at a post I created in WordPress 2.0.1 right now. There are no <br /> tags in the source post when I edit it. None. Zip. Nada.

I can edit it all I want- the only breaks occur when I create a paragraph break.

The <br /> tags I am describing in this post are added by WordPress to the body of a post when that post is created and submitted (without linefeeds). WordPress adds them. I delete them manually with the WordPress editor. They are gone forever. I can edit the post fifty times and move text around whereever I want, and they won’t reappear unless I manually insert them.

Since WordPress 2.01 seems to feel no compunction to add linefeeds (<br /> tags) to my posts when I edit them within WordPress itself, why does it do so when the exact same content is posted via the API?

Hmmm: thanks Otto42. But that seems like somewhat poor design: if the API says “don’t filter this to add further formatting like <br /> tags”, you would expect WordPress to respect that.

The strange thing, to me at least- I can go into the WordPress post editor itself and remove those extraneous <br />‘s, and that works (I.E.: It doesn’t try to stick them back in). So what part of the filtering process is putting them there in the first place?

Yes, I do. And no question is dumb: that option could have been unset ??

Bear in mind I’m referring to posting comments, not to posting blog entries. When I post a comment to my site I have no editing tools. When I (at least as administrator) subsequently edit a comment, I have the full editing set, just as I do with blog postings.

I think (?) I may have figured it out. A user can not edit their own comments. I as the post author (actually, as the admin user) can edit any comments associated with my post. At least when I created a test user (a registered user) and created a comment with that user, the account was unable to edit the comment.

If I’m right…is there any way to give a user nothing more than the ability to edit their own comments? Or am I totally confused here?

The “Add link” thing in WordPress doesn’t work with Internet Explorer. Is there an alternative that does?

Yes, I know I could use Firefox, but I like to keep my options open.