Quote:
Originally Posted by Yankidank The first thing you should do is set "you last viewed this page X minutes ago." to false. From Configure Pligg > Story (/admin_config.php?page=Story). I don't know why that is set to true by default, it seems to be a resource hog. |
I will look into changing this ASAP! Anything that will help loading time at this point is appreciated. I mean I'm losing a lot of members and reader only because my pligg site is just so slow!
Quote:
Originally Posted by gen3ric I started on shared hosting and saw a big difference when I switched to MediaTemple's (dv). BlogEngage seems to be doing pretty well so I would definitely recommend looking into a virtual dedicated solution. The nice thing about MediaTemple is that it's easy to scale as your site grows. There are 3 levels of (dv) and the basic one, which I host Design Float on, is only $50 a month. |
This is a pretty decent price for a Virtual Dedicated server. I think it's the cheapest I've seen so far! I'm assunming i wll be looking into something like this faster than I think! I really need to get my pligg site loading faster!
Quote:
Originally Posted by rwallen Your site isnt loading terribly slow. I tried loading it with nothing cached and it loads in about 15 seconds. That is close to what my pligg site is loading at (which is also on a shared godaddy account). Mine is loading at just under 10 seconds. I cleaned up some stuff on my site, getting rid of any javascript that doesn't need to be there.
Try playing around with https://addons.mozilla.org/en-US/firefox/addon/3371 |
I guess it all depends on when you visit and how many other people are also on the site! Yesterday at specific times in the day the website would only load a white screen and I continually got the errors I mentioned above! The only thing I can think of is you visited when no one else was
Thanks for that awesome link I'm installing the program now we'll see what I can learn from it
Quote:
Originally Posted by argh2xxx Even I'm on dedicated server, and I still see the errors similar to the above you had in my apache log. I think it's a bug in the pligg script and not because of the server. |
Has anyone considered trying to ix these errors? or is it too late to fix seeing we're on 9.9.0 now? Also is 9.9.0 seeing these errors as well?
If not what was fixed and how do we make it go away when using 9.8.2