Quote:
Originally Posted by Michael P  If you have support issues; please post in the respective forums, but before you go insulting the developers you might want to rethink your post before hitting submit. |
Please move this topic to the appropriate forum. I didn't see a specific section titled "support"... But I do now see that the entire lower section of the main forum page is under a "support" category. It did seem strange to me that there wasn't a section for "support", I guess I just missed the boat on that one.
Quote:
Originally Posted by Michael P By it's very nature; PhotoPost is designed to work in categories, just as vBulletin is designed to work with forums. Do you have one forum on your site that you have all your users post in? |
There is not one single topic in vBulletin that everyone posts under, but if there were vBulletin probably would select every post in that topic while only viewing a page of 20 or so posts.
Quote:
Originally Posted by Michael P PhotoPost installs with most of its featured enabled; something that the vast majority of our users want because it gives their users as many features as possible. As a site grows, it may become necessary to look at how you have your gallery laid out and which options you have enabled. It may also require additional horsepower (like a Dual Xeon setup, or more than 2gb of memory). |
PhotoPost has a great set of features no doubt. As the site grows I also agree that it may be necessary to increase the horsepower. We can add additional categories initially, but what do we do once those categories begin to fill up? Throwing additional cpu cycles in the mix will help in the short term, but not in the long.
Quote:
Originally Posted by Michael P vBulletin doesn't provide for features like film strips (or thread previews of the next and previous X threads) which require additional processing. |
Exactly why we use PhotoPost and not vBulletin for images.
My frustration is with the fact that I have pointed out what I feel is a blaring performance/design issue, and all I've received in response are suggestions to turn off the very features of PhotoPost that the users like and want. My difficult questions have been avoided/ignored. Nothing in any responses have even hinted that anyone is looking into the issue, or even that there is an issue with PhotoPost.
I understand that PhotoPost is designed with for a specific purpose, and has been designed by a talented group of people (companies aren't built by bumbling idiots). To fulfill that design, there are certain assumptions about how the end project will be used. Once we as users cross that assumption line, we are now using the software in a way it wasn't designed to be used. And that isn't something we can hold the designers accountable for.
I don't want to insult anyone, and perhaps my criticism should have been better worded. I didn't write PhotoPost, so I don't know why these queries are being ran. Also, I don't claim to know it all, and don't claim to know the solution. All I see is that it appears these queries are needlessly adding excessive database load, and to me that is a big problem.
Please help
-Nick
DigiShop Talk - Server Admin