halinagold

Please disregard the above. It turns out that this was affected by an unintended behavior from another plugin (a so called Welcome Gate functionality). Changing the setting in that plugin resolved my issue.

I have the same issue. I see the correct tags in the source code but Facebook just shows the default image even if I use the Debugger. Here’s the post: https://solosouls.net/missing-someone/

• This reply was modified 7 years, 10 months ago by halinagold.
• This reply was modified 7 years, 10 months ago by halinagold.

Thanks Dave – I appreciate it (and your response)

All the best

Halina

There is another thread on this… https://www.ads-software.com/support/topic/media-uploader-not-working-after-33?replies=20

Anyhow: for me it worked to deactivate all plugins, then activate one at a time. It was wp-stats and jetpack that created the problem. Deactivating them helped

Great point.

And, something’s definitely wrong with adding a link. I can see in the html that it removes the entire href=”https://example.com” string and in this way breaks the syntax.

I have the same problem, and also a similar one when trying to insert a link. I use Thesis for theme.

My host resolved the problem (which turned out to be a resolution you can find elsewhere on these forums – I just didn’t have the guts to change something I have no understanding about…).
The problem was due to a memory problem.
You need to add/change this in your .htaccess file

php_value memory_limit 64M

I just installed it on 2.8.1 and it looks OK.

I see 3 bugs but am not aware if it’s 2.8.1. bugs or just bugs ??

1. With a html email to the new user, slashes are being added before special characters.
2. My a href tags don’t work (I wonder it this is the same problem as the above”

3. With the admin email, %invitecode% returns a blank field

Any ideas?

Thanks –

Halina

I just did a fresh install of 2.6 and exactly the same problem is still there: No error messages, but WordPress can’t find the right paths, so the theme and the links don’t work correctly.

As I’m apparently not being supported in continuing with a Windows server the obvious solution seems to move my blogs to another domain that’s on a Linux server.
I could do that but it would presumably cost me lots and lots of traffic since these blogs have been around for a few years and I’ve been referring to them many places.

Unless… is there a way to make a general redirect (on a Windows server!) so that every time someone clicks https://www.domain1.com/oldblog/post-url they will be re-directed to https://www.domain2.com/newblog

Another solution would be leave the old blog as is (and block for comments there) and simply continue with a new blog on a Linux server…

What do you think?

Your help is much appreciated –

Halina

I just did a fresh 2.5.1 install on my Windows server, and the warning-problem is fixed. There is however still a problem with finding the right path, as wordpress apparently cannot find my themes.
When I click on the login link I’m being sent to
https://halinagold.net/?step=2/wp-login.php
which doesn’t exist.

You can view the testblog at
https://www.halinagold.net/test251

None of the suggested fixes seems to work for me.
I’m looking forward to 2.5.1

Thanks

I have contacted Akismet with the same request – no reply there either – as yet.
Until someone hopefully provides support for this issue I can’t see any other option than going to the database and manually remove all comments marked spam…

As it turned out this operation deleted my entire database – including 3 other blogs!
This is so far out – what’s wrong with 2.3 ?
Yes I do have a backup…

I have the same error on a fresh wp 2.3 installation. The only old thing here is that I imported posts, comments and categories from a wp 2.2.3 blog

I did a new installation with a new database because upgrade from 2.2.3 created first a cgi timeout error (I’ve posted this elsewhere and am waiting for support) and then apparantly corrupted my whole database.

This is unacceptable and I too will be downgrading ASAP until 2.3 gets fixed.
I’m a big WP enthusiast and am very disappointed.
I’d rather wait for a release that I can count on than hurry with a new release and then struggle with all the bugs.

I’ve never had any problems with my wp blogs previously.

Thanks a million texbiker!
It’s new to me and I love it. I think I’m going to use it regardless of the bug being fixed or not…

By the way, a direct link to the plugin page is here.

??