Classic SEO Beta 2 Released

Classic SEO Beta 2 is now available.

The second Beta version of Classic SEO has been released today. It aims to fix 2 or 3 issues reported by users.

Changes

The main changes are:

  • NEW: Add usage tracking notice and opt out
  • FIX: Variables translations in help pages will now translate
  • FIX: Fix for duplicate “view details” when GitHub updater is active
  • FIX: Fix for PHP error when refreshing sitemap in Search Console

Feedback

As always, feedback would be gratefully received especially by those experiencing the issues mentioned above.

We are nearing the release candidate stage now so feedback is especially important. There are around 20 users of Classic SEO at present which is nice, but a few more zeros on the end would be better. :slight_smile:

How to get the updated version

You will be notified of the new version in your ClassicPress dashboard.

Alternatively, you can download from https://github.com/ClassicPress-plugins/classicpress-seo/releases/download/v1.0.0-beta.2/classicpress-seo.zip.

8 Likes

As an owner of around 10% of websites with ClassicSeo, I can report, that I didn’t see any problems at this moment.

I know, they are there, just not founded yet.

5 Likes

There are no problems anywhere. None whatsoever. :slight_smile:

3 Likes

I haven’t received an update for Beta 1 or Beta 2 with Git hub updater (I am still on version 0.7). Do I just download the update it.

If so, how do I install it over the previous version without affecting any settings etc.

I’ve uninstalled the previous version and installed the new on a site without loosing (apparently) anything. For sure a backup before doing this is a good thing.
You can also export tour settings from Classoic SEO to keep a backup.
Then from beta 1 you will not need GitHub updater anymore (for this plugin).

Edit: or you can edit, in the first lines of the main file, the GitHub plugin URI to https://github.com/ClassicPress-plugins/classicpress-seo. Then GitHub updater should handle this for you.

Ah, if you missed beta1 for whatever reason, then you won’t get notified about beta2 as the small line of code GitHub Updater used has been removed because of the minor issue it created “Fix for duplicate “view details” when GitHub updater is active”.

If you are able to, then your best bet is to download the plugin from the link above. Don’t deactivate or delete the plugin from the dashboard. Just extract the zip file locally, then upload the files using FTP/SFTP into the classicpress-seo directory. You can just overwrite the files that already exist. Back in the dashboard, if you refresh the page, you should see beta2. None of this will affect your settings.

If you’re not able to do this, let me know and I’ll sort out a workaround.

Or you can use this plugin: Update themes and plugins from zip files - it also creates a backup of the previous version being upgraded/updated.

1 Like

This beta is looking really good! I’m still on Yoast, but, feeling like the switch is quickly approaching. One question that came up is: “How much time do I need to set aside to configure the plugin from the ground up?” without importing anything.

Has anyone tried this?

2 Likes

Thanks John.

It probably depends on what settings you want to use and how many posts & pages you’ve got. Setting up things like Local SEO / Knowledge Graph could take a fair bit of time. In most respects, it’d be pretty much the same as setting up Yoast from scratch.

I personally would try importing from Yoast first (take a backup first obviously - even though the plugin does this anyway) and then see how it looks. It does a pretty good job of importing from Yoast but there’ll still be stuff to do afterwards.

Maybe others could chip in with their experience?

2 Likes

Fair enough. I’ll probably do it over a weekend, so, I don’t have to schedule it in. I’ll be sure to let you know how it goes. I appreciate the import options, but, tend to avoid them. My reasoning is that if I import, it’s likely I’ll miss setting up (or finding) other things. By going through and doing it manually, I’ll be forced to become an expert. :wink:

2 Likes

Thanks, this worked fine for me. Downloaded the zip and uploaded to the folder on my host.

Everything installed okay, and at first glance, everything looks to be okay. Did I read right that I do not need github updater anymore.

Many thanks

2 Likes

Yes, you can remove GitHub Updater now - unless you’ve installed it for other plugins of course. But Classic SEO no longer needs it.

Yeah, that’s fine. It’d be good to hear of your “start from scratch” experience anyway.

Thanks for the beta 2. Here are my tests:

  1. The upgrade from beta 1 went great.

  2. The PHP error is fixed. Everything is fine.

  3. ClassicSEO is a stable plugin even before the beta. I moved to it a few weeks ago and it created no problems with ranking my site. What’s more: The transition process made me think of the content of my site differently. I certainly recommend it to the entire ClassicPress community.

  4. Тhe problem with the help\variables is solved, although there are 2 strings omitted in the translation file.

As I focused on the translation file, there were a few minor omissions in it:

  1. It has references to the Wordpress Dashboard in several places. Could not find exactly where they appear. I think it is correct to replace them with the ClassicPress Dashboard.

  2. Missing strings in the Help\variables tab:

  3. minor missing string in SEO Settings\Breadcrumbs:

  4. I think this is related to the new version:

  5. I have a translation problem here, but I don’t know if it’s due to the Wordpress theme I use:

  6. And a small string in the administration of Classicpress press\ plugins.

Certainly several translation strings should not be a priority. I describe them because I noticed them. They have no real impact on working with ClassicSEO.
Thanks again for this plugin. It’s great that the ClassicPress has this solution and is independent.

5 Likes

Really???

My suggestion is to import, because if you configured something in Yoast, chances are they will be imported, it will save time by a margin.

Then, you will need more time, than with Yoast to familiarize and configure the rest settings, because there are a lot more options. It’s a completely different beast, and some settings can be not so obvious.

1 Like

OK, not a bug, but a small feature suggestion:

In Titles and Meta, Global Meta, “Separator Character” would be nice to have an ability to set custom character. This is the only one feature that exists in Yoast but didn’t in CSEO.

1 Like

@CodePotent,

It largely depends on the site. I left Yoast a year ago and I don’t know what changed there during that time. For a site with about 50 pages / posts, it took me about 2 days for basic setup and about another week for adjustments to my content on some posts. I have corrected some of the publications because the analysis of Yoast, SeoPress and ClassisSEO is different and this was a way to look at my content in a new way.
Although setting from scratch you might want to save your keyword information in some way … it will save you effort.
In my case, Yoast and SEOPress had left a lot of junk in the database and I lost a few more hours to clear.

1 Like

Thanks @KokoFresha. The translations feedback is really useful and I’ll aim to get them fixed for the next release. And thank you for your other comments too. It’s great to hear that it’s working well for you.

1 Like

This is something I’m aware of myself and something I plan to look at after v1 along with better help text. I may try to consolidate some settings and make things a little easier to understand.

Do you mean breadcrumbs separator or titles? As far as i can tell, Yoast doesn’t have the option to set custom separators for titles but it does for breadcrumbs. Classic SEO has neither.