catalinfx

That’s weird. Maybe some server issue, but I didn’t update, and it doesn’t update automatically.
What I see in the logs is some sort of error because wp-json points to PATH/index.html, while trying to access the URL for redirection.

Notifications are not the problem.
Their FREQUENCY is.

I’m expecting them to go after being notified. But they come back and ruin my WordPress experience. I can always see the red bubbles and I always think there’s something wrong.

When you close a notification, it shouldn’t be coming back for a while.

Yoast’s are there to stay.

And THAT shouldn’t be allowed.

If every plugin maker would’ve done the same, people would’ve ran from WordPress altogether.

Agreed?

So why YOU do it and others don’t?

Given up Yoast for Rankmath for now. See if you can fix something out. Then I might reconsider.

That’s the definition of losing clients. You’re welcome for the feedback.

Good luck.

• This reply was modified 3 years, 2 months ago by catalinfx.
• This reply was modified 3 years, 2 months ago by catalinfx.

@maybellyne it doesn’t work

It’s more aggressive than ever and really annoying. Even if you want to get rid of it by clicking on the “eye”, it comes back real quick!
There must be a problem with your notifications. It’s never been like this, no other plugin does that.

I will complain everywhere about it, till you stop! You should’nt be allowed to do that!

We all get your messages. No need to be aggressive about it. Is like a fist in my throat. REALLY ANNOYING.

I have a feeling this can be fixed from Pods, used to create the custom taxonomy.

As per my initial request, I can confirm the code provided and used within my theme’s functions.php works perfect with Pods. My custom field displays in URL exactly as advertised, using %__my_custom_field_slug%.

This may be marked as solved.

Bought it just now, thank you very much.

See you on “the other side”! ??

Outstanding!

I’m doing a revamp of my website’s design, plus a migration from Drupal 7 to WordPress. Now, for development, I’m using a different domain. My production site is globi[dot]ro, but my development site is set onto globi[dot]site. Note the extension is different, I can’t keep my website offline and I don’t want to use subdomains either. Does it mean that I have to buy a license for two domains? Can we work this out? The .site is just a development domain I’ve bought for this exact reason, nothing else. The .site domain won’t be used for production.

I am writing this here because I’ve used the contact form on the site and there was no answer. Here, on the other hand, you are as helpful as it gets.

I assume Toolset needs a snippet as well?

This worked for me:

Updated WP to the last version.
Updated plugins.
Made sure I have the right PHP version (7.2 in my case, because 7.0, 7.1 are obsolete and 7.3 throws me some errors sometimes on shared hosting).
Went to Permalinks settings, already had Post Name there, but pressed ok anyway.
Hard refreshed the page.

Modified a page adding a few keywords and it worked.

Some of the steps may not be necessary, but updating PHP and WP is the right way to maintain a site anyway.

best of luck!

• This reply was modified 4 years, 9 months ago by catalinfx.

@yaniiliev
It doesn’t do anything for free without installing your self-hosted plugin.
So without your other code, NSFW IMHO, it’s just a bridge to your business.

@yaniiliev
So you agree with me that this plugin in THIS form, can’t be used for free?
Needs additional plugin installed and that plugin is not part of WP repository.

@yaniiliev
I think one of us is losing it, cause from where I’m standing there’s no FREE & SAFE, Opensource import option.
What are the FREE options right now? WITHOUT additional plugins.
– For File import you have to install a third party plugin that never went through WP’s security scan
– The rest are all paid

• This reply was modified 6 years, 4 months ago by catalinfx.
• This reply was modified 6 years, 4 months ago by catalinfx.

Done the same thing to make it work once more.

1. Logged in my host backend (using cPanel / FileManager in my case)
2. Browsed to reach website root
3. Accessed the plugins folder /wp-content/plugins/ in my case
1. Renamed the /wp-content/plugins/autodescription/ to /wp-content/plugins/.autodescription/
2. Logged in to WP backend
3. Installed the new version of the plugin
4. Reloaded the website to check if it is working – and it does
5. Deleted .autodescription folder.

Settings seems unchanged. Is there a chance something else must change to keep all the metadata (descriptions etc) the same, for SEO sake?