Dangerous Stack Trace Is Dangerous

An error has occurred

Internal error (version: 10.0.3, PHP version: 5.6.8, URL: /composr/index.php?page=start&type=_editor&id=forum&keep_fatalistic=1&wide=1)

You have turned on stack traces for all errors, via having keep_fatalistic=1 in the URL. This means that this may not actually be a fatal error, you have just asked for it to be presented as such (perhaps to help you find where it came from).

Here is the stack trace:

Below is a stack trace revealing the state Composr was in when the error occurred. If this represents a bug in the unmodified software, you may want to check Composr website for a fix, and if there isn't one, report this as a bug. Please note that merely posting a stack trace is not sufficient for us to solve your problem; the stack trace is just an aid that presents us with additional information. We still need to know the error message, what you tried to do, how you tried to do it, version numbers, and any other appropriate information.
We apologise for this problem and if it's a bug we hope you will work with us so that we can fix it for you promptly.

File	'/home/mythus/public_html/composr/sources/failure.php'
Line	977
Function	'get_html_trace'
Args

File	'/home/mythus/public_html/composr/sources/global2.php'
Line	950
Function	'_fatal_exit'
Args	Tempcode -> Internal error

File	'/home/mythus/public_html/composr/sources/failure.php'
Line	397
Function	'fatal_exit'
Args	Tempcode -> Internal error

File	'/home/mythus/public_html/composr/sources/global2.php'
Line	934
Function	'_generic_exit'
Args	Tempcode -> Internal error 'WARN_SCREEN' false

File	'/home/mythus/public_html/composr/sources/templates_pagination.php'
Line	73
Function	'warn_exit'
Args	Tempcode -> Internal error

File	'/home/mythus/public_html/composr/forum/pages/modules/forumview.php'
Line	203
Function	'get_keyset_pagination_settings'
Args	'forum_max' 20 'forum_start' 'kfs' 'sort' NULL 'get_forum_sort_order'

File	'/home/mythus/public_html/composr/sources/zones.php'
Line	791
Function	'run'
Class	'Module_forumview'
Object	O:16:"Module_forumview":5:{s:5:"title";N;s:2:"id";N;s:10:"forum_info";N;s:11:"breadcrumbs";N;s:12:"of_member_id";N;}
Type	'->'
Args

File	'/home/mythus/public_html/composr/sources/site.php'
Line	1,181
Function	'load_module_page'
Args	'forum/pages/modules/forumview.php' 'forumview' Tempcode -> …

File	'/home/mythus/public_html/composr/sources/site.php'
Line	1,253
Function	'request_page'
Args	'forumview' true 'forum' NULL false true Tempcode -> …

File	'/home/mythus/public_html/composr/sources/site.php'
Line	891
Function	'request_page'
Args	'start' true NULL NULL false false Tempcode -> …

File	'/home/mythus/public_html/composr/index.php'
Line	78
Function	'do_site'
Args

Automated fix message

Chris Graham said

Wordpress is ideal for a simple site that consists of blog posts and pages. It's strength is that the simplicity facilitates:

1. Really beautiful content, as features don't get in the way of really nice graphics – e.g. really good images and use of white-space and typography. It's great for brand websites.
2. Availability of lots of themes, as themes don't have a whole lot that they need to style. This is related to the above. It's relatively easy to make a beautiful Wordpress theme and very easy for people to install it.
3. People without a lot of skill to setup and maintain a simple but attractive blog.

Some teams will push Wordpress beyond what is reasonable, and that is really messy, but it's understandable as they want to focus on one technology base for their clients.

Joomla is built to be extendable in a cleaner way than Wordpress. Its popularity has reduced though as Wordpress has got more sophisticated, it's been getting squeezed out I think. It's still very popular though and has many really sophisticated addons.

Drupal is a much more complicated system ideal for programmers who don't want to write their own CMS but expect to be doing a decent amount of custom coding. It's a good choice for higher budget sites with teams of well-paid coders.

Composr is probably most comparable to Joomla. However unlike those 3 we focus on having a lot of features available out-of-the-box and well-integrated. Composr is a great choice for people who can't afford to hire a Drupal development team, but don't just want a simple blog.

Because Composr has a lot of features, it does bake in more assumptions than Drupal does. The code is very terse so that performance is maintained, and so that we don't need 10 million lines and an incomprehensible architecture to implement all we need. If a team is building something really custom or complex they may prefer the cleanness of Drupal, requiring a lot more expertise (i.e. cost) but coming to a cleaner end point.

So to summarise…
Wordpress = Great for simple beautiful websites, often pushed beyond its limits
Joomla = Mostly squeezed out by Wordpress, but its cleaner API allows more sophisticated addons and it has many
Drupal = Complicated and expensive, but maintainable for complex custom projects in a way no other system is
Composr = Very broad functionality, very cost-effective so long as that functionality aligns well with your project

I've tried to be honest in my assessment. Any of these systems might be the right choice for any individual group, it really depends on their needs and their budget.

Personally I'm trying to encourage the promotion of all these Open Source CMSs as great tools depending on what you are needing, while also letting people know just how feature-packed and efficient Composr is compared to them.