Updating PowerMessenger

Before I dive right in and start updating PM, I wanted to ask if there where any outlined steps or issues?
I don't mean, updating from v 1.0 to v 1.2. It's already using the last version issued.
I am referring to the fact that none of the security rules are recognized when I try to access them and I need to update the includes so they use the webassist/ directory of the latest extensions.

I've done this several times before on other custom pages but I wanted to make sure that none of the PM pages need special attention to this update since the files are several years old.

Also, there is a Super Administrator mentioned in the login page. But I do not see that rule defined in HelperGroupsRulesPHP.php. Is that intentional? I'm wanting to add a higher admin so that certain menu items such as "Settings" are hidden from the admin that simply creates the mailing lists.

Thanks
TroyD

I would sugest using Power PMCS Builder form Design extender to create CMS that is using the most curent version.

It sounds like you are using an older version that uses the WA_SecurityAssist/HelperGroupRules.php file. the super admin rule should be defined in that file.

if you where using the most recent version it would be defining the rules in the webassist/security_assist/helpergrouprules.php file.

Jason,

What is the latest version of PM? In my account it's v 1.0.2 released back on September 27, 2012. And I see no upgrade option so I assumed it was the latest version.

The download still uses the old extension directories ("WA_...").

You mentioned using Power PMCS Builder instead. Would I be able to maintain all of the clients templates, emails campaigns, users, opt-ins, etc, when trying to convert this to use a newer CMS?

Thanks,
TroyD

Sorry, I misread this initially and thought your where talking about Power CMS, now i realize you are referring to Power Messenger.

Power Messenger 1.0.2 is the latest version available, yes, it does use the old structure, you would need to manually update this to use the new structure for files in the webassist folder.

Ok. That makes more sense then. I wondered how that would be the right route to take with it.

I don't mind updating this by hand but wanted to make sure I didn't need to watch out for any known issues with the license validating, or user logins after I update this.
Since it's on a production site, it's pretty important that I don't break it. I guess I can just restore this to my local server and work from there first.

Thanks,
TroyD

"I guess I can just restore this to my local server and work from there first."

Yes, that would be the best rout, test on a local site before making modifications to the live site.


This sort of Update is not one that we support, nor do we have documentation for it, so there would not be any known issues since it is not a scenario we have tested.