The following warnings occurred:
Warning [2] Undefined array key "allowautourl" - Line: 584 - File: inc/class_parser.php PHP 8.1.31 (Linux)
File Line Function
/inc/class_error.php 153 errorHandler->error
/inc/class_parser.php 584 errorHandler->error_callback
/inc/class_parser.php 228 postParser->parse_mycode
/printthread.php 203 postParser->parse_message
Warning [2] Undefined array key "allowautourl" - Line: 584 - File: inc/class_parser.php PHP 8.1.31 (Linux)
File Line Function
/inc/class_error.php 153 errorHandler->error
/inc/class_parser.php 584 errorHandler->error_callback
/inc/class_parser.php 228 postParser->parse_mycode
/printthread.php 203 postParser->parse_message



GetSimple Support Forum
Using GetSimple for bigger sites - Printable Version

+- GetSimple Support Forum (http://get-simple.info/forums)
+-- Forum: GetSimple (http://get-simple.info/forums/forumdisplay.php?fid=3)
+--- Forum: General Questions and Problems (http://get-simple.info/forums/forumdisplay.php?fid=16)
+--- Thread: Using GetSimple for bigger sites (/showthread.php?tid=1692)



Using GetSimple for bigger sites - retrofan - 2011-05-11

Hi,
are there performance or other stability problems to expect, when serving a frequently visited bigger site (ca. 1000 unique visitors per day, lots of pages)? In my viewport it must be even converse. Until today I used modx, typo3, joomla and other sql-based systems. But I see no reason, why not simply install GetSimple instead of those oceansteamers Smile Functionality is not my problem - some interfaces have to be coded by me regardless which system I will chose. I just want to know if there will be problems with perhaps file-locking while editing and storing a page while visitors request the same page several times and things like that?

Any hints?


Using GetSimple for bigger sites - yojoe - 2011-05-11

Hmm... Mike mentioned he was successful to operate on 2k pages.
If you won't serve content dynamically, I'd give it a hit along with a content, and menu caching plugins (there are couple).

Be aware that caching content while giving access to it for large audiency might choke the website a bit.
I'd hide the page firstly -> commit edit -> unhide page.
But from the other hand whole cache is resaved during every page edit.

That's for technical things.
But how do you want to achieve workflows and tons of other things remains a riddle for me.
For such demanding website GS is more a framework offering simple management.