Postnuke Integration Does Not Work with Current Version

[damon18]

I haven't been able to upgrade my Postnuke site to the latest version 1.12 because the latest version of Photopost Classifieds comes with a Postnuke integration that is now two years out of date (Postnuke ver .764).

It's been that long since Postnuke reached version .8 and changed it's name to Zikula, there were several major changes in the user table that affect the integration. Download the latest files from here.
Homepage :: Zikula Application Framework :: Fast easy and free - Do you dig it?


Please create a integration file that will work with Postnuke/Zikula, or state that you will no longer support Postnuke (and remove it from your feature list) so I can find another classifieds solution.

[damon18]

Also wanted to mention that if you need it I would be glad to do a fresh install of Zikula on an empty domain on my server and give you server access for testing an integration.

[Chuck S]

We integrate with Postnuke. Zikula is another project loosely based on postnuke. There are many flavors out there but we only support the true Postnuke integration.

About :: PostNuke :: Flexible Content Management System

This is what we support above. Read there own note on the postnuke site.

Zikula should not be confused with PostNuke since they are spearate products and the underlying code is vastly different.

Thus postnuke which we supported ended which means our support of that product ends with the version we last supported which was there last version 7.64

I can tell you working on another integration is not going to happen anytime soon. We currently at this time have an active PhotoPost Pro 7 Beta going on as well as working on the new vBulletin 4.0 Beta integration which about 40% of our customer base uses.

I work on new forum integrations in my free time when not coding our actual applications and providing product support.

[damon18]

I understand your position, but it's a serious problem for me.

I think if you would look at the current code you would see that the user code for Zikula is very like Postnuke, but some user database changes have been made because they have better separated the login process from user profiles.

The info on Postnuke.com is poorly worded, probably because of language issues. The project changed it's name to Zikula and continued with planned code changes, which would have happened even under the Postnuke name. The project didn't have control of the Postnuke country domains around the world and that was a big reason for the name change. It's not a fork or new project.

[Chuck S]

The End :: PostNuke :: Flexible Content Management System

Thats very clear to me. They are completely different projects. If we had an issue with a supported integration I could look into your issue but this is a new integration entirely that we do not support. I wish I could help but at this time we are in a beta cycle of Pro 7 and checking into the anticipated vb 4.0 release which covers 40% of our customers. I solely look into new integration in my free time which at this present time is not much.

[damon18]

Clear or not, I can only tell you as a Postnuke user since 2002 that Zikula IS the latest version of Postnuke.

If you don't want to (or can't) support the new version I can't make you.

I'm only asking as a paying customer to be able to continue using the product I have purchased and payed for annual support.

I've tried to edit the postnuke.php file myself, it appears that just some table names need to be changed and maybe the way cookies are handled, I have been able to get it to the point that classifieds recognizes Zikula users and groups, but they won't stay logged in in classifieds.

[Chuck S]

Damon

If you where using postnuke I would have no problem assisting you in a support manner because that is a product we support.

Zikula should not be confused with PostNuke since they are separate products and the underlying code is vastly different. A decision was made to provide security updates for PostNuke until 1st July 2009 and there will be no more releases of PostNuke beyond version 0.764.

That quote right off the postnuke site states there are no releases of postnuke from the one we already support. I know we support 7.64 of Postnuke.

[damon18]

Like I said, I can't make you do it, but you are just being stubborn now. I've already explained the name change. If the quote was accurate it should say "no more releases named PostNuke beyond version 0.764".

You'll have the last word no matter what I say, you always do.

[Chuck S]

I have to go by what the PostNuke site says. PostNuke site says Postnuke ended with version 7.64. This has been clearly listed on the Postnuke site.

there will be no more releases of PostNuke beyond version 0.764

The Postnuke site is very explicit in the information they give on its end. They tell you David Baum made a fork or new rendition based on Postnuke and it spirals off into its own project

PostNuke started officially in the summer of 2001. After several years of development the PostNuke came to an official end in 2008. The software was always meant to be the stepping stone to better things, namely the "Adam Baum" project which was originally based on a PostNuke version but soon forked in a totally different direction under development for a few years.

The "Adam Baum" project as it was called is what has become Zikula. This is a totally different software from Postnuke as you have found out.

Its like this I never said we would not eventually support Zikula. I have stated I make new integrations in my free time thats all. My time here is spent providing product support and right now we have an open beta of our Pro gallery software. We are also working with the new vb4 project which 40% of our customers use.

Thus with everything on our plate right now we do not have time to look at a brand new integration at this time which is what i said. Thats doesnt mean a few month down the line when our gallery beta is over and vb4 is gold and our workload is back to normal that we will not write some more new integrations.