[Solved] SEOTools2 and CMSMS 1.11

[psy]

With the release of CMSMS 1.11 it seems that Smarty3 naming has a problem with the module name SEOTools2. See Calguys comment at http://forum.cmsmadesimple.org/viewtopi ... 79&t=61847 Not even SEOToolsTwo would work so I have updated the module to be called SEOToolsToo which does.

Looking for advice from the dev team and/or forge admin as to what to do in the forge to make it accessible to the community.

The original SEOTools does not work with 1.10+ and the developer no longer maintains it however it remains available in the forge. This was the #1 reason for the SEOTools2 fork.

Now SEOToolsToo is needed. I have not yet and not even sure if I should create an upgrade path. It is essentially a new module. Should I:

[1] Request a new project. This will leave 3 variations of the module in the forge, one of which does not work with the two CMSMS latest releases.
[2] Make it a new release under SEOTools2, renamed SEOToolsToo with clearly marked comments that it is not an upgrade

Please advise.

In the meantime, anyone wanting a copy of the new SEOToolsToo for CMSMS 1.11 can PM me for a copy.

Thanks
psy

[postiffm]

psy--

Do you think that the following error would be fixed by your new edition of SEOToolsToo?

Call to a member function GetURL() on a non-object in /home/pr368398/public_html/cms/modules/SEOTools2/action.default.php on line 72


To answer your question, it seems like we should have ONE package named SEOTools, and the version number/dependency system takes care of letting the user know that "if you have CMSMS 1.11, you need SEOTools version X" and "if you have CMSMS 1.10, you need SEOTools version Y" and "if you are not using a supported version of CMSMS (before 1.10) then forget using SEOTools!

[psy]

There is a workaround solution to the error in the forge thanks to leeroybrun. This will be incorporated in the next version.

Yes, I agree, there should only be one module, SEOTools in the forge however the forge guidelines state that if you fork a module, you must give it a new name, hence SEOTools2.

I'm unsure if the error in action.default.php is the cause of the templates not saving. Fixing the error will rule out that possibility.

Thanks for your feedback.

[berg3n]

Same problem for me iam not able to save the template with {SEOTools2} in it. The module seems to work if put {SEOTools2} in in content...but i only get blank page when saving if i put in the template.

Have anyone been able to try the new version?

[postiffm]

As a temporary work-around, go to Extensions | Modules and click the green arrow in the Active column to deactivate that module.

Also comment out your {SEOTools2} call, like this:

<!--SEOTools2-->

(get rid of the curly brackets and put the comment delimiters.)

Then you can do whatever you want with your site, sans SEO for now, until a new edition of the SEO module is available. You should be able to save your templates now.

[psy]

Thanks postiffm, yes deactivating the module for now will allow you to keep working on the templates.

I've narrowed down the trouble spot to something in action.default.php that is clashing with CMSMS 1.11 & 1.11.1. Will post here when I've found the culprit and issued a new version.

psy

[psy]

New version of SEOTools2, compatible with CMSMS 1.11+ is now available in the forge. http://dev.cmsmadesimple.org/project/files/1087

Thank you to all who helped with the update, in particular leeroybrun and postiffm.

[berg3n]

Nice it seems to work Big thanks

//Jonas

[postiffm]

I'm trying to check it out as well, but somehow my host has the modules/SEOTools directory with owner/group as nobody instead of myself, so now I don't have permissions to overwrite the files!! Stand by...

[postiffm]

File permissions are fixed...now I try to upgrade the SEOTools2 module. When I click "upgrade" I get this:

Fatal error: Call to a member function GetName() on a non-object in /home/pr368398/public_html/cms/lib/classes/class.moduleoperations.inc.php on line 827

Oops. Perhaps the module being deactivated causes this? So, I'll activate it (click the check mark to make it green) and try the upgrade again. It works!

I've played around with the 1.0.11 version of SEOTools2 now and it seems to be working as advertised. Thanks psy.

[postiffm]

In version 1.0.9 of SEOTools2, we had this (from Prue Rowland):

"The ability to add any Active pages, not just those also marked 'Show In Menu', is in release SEOTools2 version 1.0.9. You need to go into Content->SEOTools2, Page Settings tab and enable the pages in the Indexable column."

What happened to the 'indexable column' in the OneEleven themed admin console? Has it vanished?

[psy]

Hrrmmm... It's still there on my sites, in fact it now displays the word 'toggle' next to the tick and works fine.

Thanks for the feedback. Will do some more digging.

[postiffm]

OK...I'm blind. It was WAAAAY off to the right hand side and my quite-wide browser window was not wide enough to display it. False alarm.