Due to changes that Constant Contact has made regarding authentication in their API, it has become necessary for us to update our Constant Contact Helper Extension that comes with all of our Constant Contact Extensions that use their API.
As of March 31st, 2022 users will no longer be able to connect to Constant Contact services without updating.
Unfortunately, there wasn't much notice given of this change and we have been working diligently to make the needed changes to our plugin. We are polishing the last minute changes and finishing the in-depth testing needed to make sure we deliver a top-notch product.
Please check back as we hope to have the updated plugin available as soon as possible. Additionally, we will be offering a 50% discount coupon to all users regardless of their current subscription status.
Use the Coupon Code: CCHALFOFF
We are in the process of updating our Constant Contact products with the latest version of their API.
With the release of the Constant Contact API v3, we will need to completely rewrite our extensions for compatibility with the new API. We hope to have this completed in the next few weeks, so look for the newly updated extensions and update to get the full benefits of this new API.
UPDATE: This process has taken far longer than we could have anticipated. Please be patient while we continue to make the neccessary changes to our Constant Contact extensions so that they can use the latest API.
This is the process in which we upgraded our forum from Agora to Kunena, and the issues we encountered.
As always, the first thing we did was install everything on our development server. Next, we followed the directions given by Kunena to perform the conversion from Agora to Kunena which included installing an older version (1.5.14) because the latest (1.6.3) was not compatible with the converter. That's where our first issue showed up. We could not get Kunena 1.5.14 to install. We searched Google for some answers, but found none. Somedays you win and find exactly what you need, other days you give up only to try again later.
Later came and we found a post that said to download Kunena 1.5.13 instead. We had a little trouble finding it (mostly because our frustration level was high and we didn't read the directions thoroughly) but once we did and installed it, everything fell right into place. Next, we installed the Kunena Converter and ran the process to migrate Agora. Worked like a charm. The last step was to upgrade the Kunena installed version of 1.5.13 to the latest (1.6.3) That went well too!
One day out of the blue (so we thought) all of our downloads broke. No one could access any of our downloads via the DocMan 1.5 component. After two days of server migration (actually moving our site to a different host) and troubleshooting, this is what we found:
I had forgotten two of the most helpful tools in debugging any system:
1) Error Logs and messages
2) Asking myself the question: "What was the last thing I changed?"
I have found the practice of setting the Joomla "Error Reporting" Global Configuration to "System Default" to be good. However, when I need it, I forget to change it to something more useful, like "Maximum".
We recently had a client who needed to convert their WordPress website to Joomla. Their forum was vBulletin and they used aMember to manager their users. During our initial research, we discovered there was not a direct migration path to Kunena, however, we found that migration was still possible if we converted vBulletin to phpBB3, then to FireBoard (a predecessor to Kunena). Once we had a Joomla 1.5 website set up with FireBoard and a successfully migrated forum, we upgraded to Kunena 1.6.x. (We hope to add basic instructions as to what we did at a later time)
We ended up having to modify the phpBB3 converter script so that the aMember user data was imported into JomSocial (the replacement of aMember) along with making changes to the converter for phpBB3 to FireBoard. All in all, we were very happy with the results.
One of our clients needed a way to automatically create user profiles on their Joomla website from records that are created in their FileMaker Pro database by the sales staff. Once their new members have signed up in the office, they can 'flip a switch' that now automatically creates their Community Builder Profile. Once the new members arrive home, their profile is waiting for them, all they have to do is confirm their email address and they are ready to log in.
Our client also wanted to be able to have these new accounts sign up with Constant Contact, and with our , the signup to their newsletter is automatic too!
We found this article of interest discussing one of the newest features in Joomla 2.5
Give it a read...
We have found the Joomla Extension " ReDJ" highly useful, not only for our websites, but for our clients as well.
We had a site that required us to map every page that the client had created in XOOPS, and although we were able to accomodate most page names simply using the 'alias' of an article and menu, this component allowed us to remap the entire site without one broken link.