Originally Posted by omegatron
Just a clarification. There are many sites running nuke. The only error was the bbranks thing and that mainly happened because we were never notified it changed. Things like that happen in integrations. There was only one error.
BTW: (I mean to say this with the utmost respect, but it's going to sound bitchy no matter how I put it): I posted about it twice, once buried in a response to someone and once flat out in the bugs forum, and I still had to mod my upgrade weeks later. If it has since changed, my apologies, but I haven't upgraded since then.
Photopost claims to integrate with forums. Since the forum with Nuke is phpBB we integrate with that. We do not integrate with the CVS part of nuke. There we look for the admin user in the forum user table with the proper user_level for an admin. We also do not run as a module. There are no errors runing photopost with nuke. I think your apprehension comes from the fact we do not run as a module.
I don't think "apprehension" is the right word, but here goes:
I know it doesn't work as a module. That's why I switched to a module gallery and I suggest anyone with a phpnuke CMS do the same. That's not to say that I didn't like Photopost. On the contrary, I think it's the best on the market if your site is primarily a forum and a gallery and that's all you want it to be. You can quote me on that. That's what my site was and everyone loved it back then.
If your site evolves, however, and the CMS most comfortable to you turns out to be phpnuke, after fielding complaints and constant questions from my members (several a day even when I had less than 50 people), you would be better off just switching to a gallery designed for a php-nuke CMS and forgetting about the money you spent. I am lucky enough to have a site powered by a small core of rabid fans who want the information so badly they actually tell me when there's a problem instead of abandoning their accounts like most of us do when we get frustrated, so I heard a lot of them. They even PM'd me at other related sites about the login loop.
I didn't mean the other bugs were inherently Photopost's fault, but having a gallery designed to be used with my CMS gets rid of them. Off the top of my head when I was using a plain Iframe module with a clean install of phpnuke 7.0: Login Loops:
You have to get people to set their cookie levels lower for the gallery than for your main site, which is like pulling teeth for some of them, and anyone running on AOL or certain other browsers has to log in seperately for the forum and the gallery and clear their cookies to log out. This isn't PP's fault, obviously, I blame AOL's roving cookie sessions, but getting rid of PP got rid of the problem. Obviously no one can design a product that works on every browser and with every combination of supporting software and scripts. Multiple registrations:
Every upgrade I would have had to comment out the register button because the aforementioned login loop caused some people to believe they had to register seperately for the gallery, then they got stuck between usernames. These people all appeared to be over 50 and my site was one of their first steps outside emailing the kids and AOL. All they know is that cookies are bad. Maybe sites with a younger audience are used to doing their own cookie troubleshooting. In any case, getting rid of PP got rid of the problem. Profile:
The profile link had to be commented out because it went nowhere in phpnuke 6.5. If this is no longer the case, my apologies, but clearly it's been awhile since I attempted an upgrade. I believe this to be the fault of the ported version of phpbb used in the phpnuke CMS, not Photopost, but, yada yada yada. Usergroups:
The usergroups were in a complaint class all their own. All of these seemed to be a conflict caused by a mix of Photopost, phpnuke, the ported phpbb, AOL, sometimes Mozilla, and Norton. Again, not PP's fault per se, but getting rid of it gets rid of the problem. Uploading, Comments and Showphoto:
Some people had to be re-added to a usergroup manually in order to upload and view. I believe this is an AOL/Nuke session cookie conflict. Not PP's problem, but it went away when I got a nuke gallery. Complaints about the theme:
I know you were working on changing it when I left. My apologies again if you are now able to integrate a theme just by adding the cms. It was a chore before, especially when everything changed during the last upgrade I tried. I lost someone for awhile because she couldn't use the high-contrast large print theme she could use elsewhere on the site. Other notes:
Three people in Europe would be locked out of the main site if they logged in at the gallery first. I still have no idea what caused this, but I doubt it was Photopost. But when I got rid of it they couldn't log in there first....
You're going to be dealing with the Authors/Users Admin thing every time someone tries to upgrade to a phpnuke CMS (which they will attempt even if you tell them not to) unless you add it to your FAQ and upgrade readmes. (Actually, considering how many people read those, you may still have to. I don't envy you support people. After fielding all these complaints I don't know why anyone would volunteer for it.) Obviously that's not PP's fault, it's the ported phpbb, but you don't have that problem if you use a gallery designed for the phpnuke CMS.
The only complaints I've had about the new gallery were right at the beginning when I missed a chmod and when I forgot to reinstate a moderator.
I'd like to stress that it's not that I didn't like Photopost. I did very much, so did my members before we decided on a more interactive site to digitize our collections. But after that it required too much hacking and explanation on my part when what I really wanted to do was just run my site. I tried to keep it, it didn't work well with the new system, so I switched. If other people want to spend the time to get it to work where it isn't meant to, more power to them, it's a good cause and a great gallery, but for the average person who doesn't want to spend all of their off time hacking it's better just to abandon it. Coppermine isn't as sexy, but it does nearly all the same things.
My core members were more than happy to upload all of their pictures again and start over with comments and ratings if it meant a more dependable ride. I installed the other gallery before removing the link to the old one and the vote was unanimous in favor of the switch.
I suggest people who aren't getting many complaints check their user tables and see how many of their members came back after registering. My activity went way up after word got out I "fixed" my gallery. Sure, they just look and download, which is what my entire site is there for, but at least they come back and are able to get what they want on the first try.
P.S. Please remember I don't mean to imply Photopost itself is bad, but it shouldn't be married to a phpnuke CMS.