News + realURL + i18n in Typo3 = cHash error
up vote
1
down vote
favorite
I managed to make news (tx_news) work realurl under the default language. Then I wanted to localize the news, so I created transaltions for them. However when I access the list view for a non-default language, it fails with
Request parameters could not be validated (&cHash comparison failed)
The failing link does not contain cHash, it looks like this
http://host.com/mysite/en/about-us/
What could be the cause and how to fix it? Here is the realURL setup
$GLOBALS['TYPO3_CONF_VARS']['EXTCONF']['realurl']=array (
'_DEFAULT' =>
array (
'init' =>
array (
'enableCHashCache' => true,
'enableCHashCache' => 1,
'respectSimulateStaticURLs' => 0,
'appendMissingSlash' => 'ifNotFile,redirect',
//'adminJumpToBackend' => true,
'enableUrlDecodeCache' => true,
'enableUrlEncodeCache' => true,
'emptyUrlReturnValue' => '/mysite/',
),
'pagePath' =>
array (
'type' => 'user',
'userFunc' => 'EXT:realurl/class.tx_realurl_advanced.php:&tx_realurl_advanced->main',
'spaceCharacter' => '-',
'languageGetVar' => 'L',
'rootpage_id' => '1',
'firstHitPathCache'=> '1',
),
'preVars' =>
array (
0 =>
array (
'GETvar' => 'L',
'valueMap' =>
array (
'cs' => '1',
),
'noMatch' => 'bypass',
),
),
'fixedPostVars' => array(
'19' => array(
array(
'GETvar' => 'tx_news_pi1[controller]',
'noMatch' => 'bypass',
),
array(
'GETvar' => 'tx_news_pi1[action]',
'noMatch' => 'bypass',
),
array(
'GETvar' => 'tx_news_pi1[news]',
'lookUpTable' => array(
'table' =>
'tx_news_domain_model_news',
'id_field' => 'uid',
'alias_field' => 'title',
'addWhereClause' => ' AND NOT deleted',
'useUniqueCache' => 1,
'useUniqueCache_conf' => array(
'strtolower' => 1,
'spaceCharacter' => '-',
),
'enable404forInvalidAlias' => '1',
'languageGetVar' => 'L',
'languageExceptionUids' => '',
'languageField' => 'sys_language_uid',
'transOrigPointerField' => 'l10n_parent',
),
),
),
),
),
);
php typo3 realurl
asked Jan 20 '14 at 19:01
David Apltauer
3831820
add a comment |
up vote
1
down vote
favorite
I managed to make news (tx_news) work realurl under the default language. Then I wanted to localize the news, so I created transaltions for them. However when I access the list view for a non-default language, it fails with
Request parameters could not be validated (&cHash comparison failed)
The failing link does not contain cHash, it looks like this
http://host.com/mysite/en/about-us/
What could be the cause and how to fix it? Here is the realURL setup
$GLOBALS['TYPO3_CONF_VARS']['EXTCONF']['realurl']=array (
'_DEFAULT' =>
array (
'init' =>
array (
'enableCHashCache' => true,
'enableCHashCache' => 1,
'respectSimulateStaticURLs' => 0,
'appendMissingSlash' => 'ifNotFile,redirect',
//'adminJumpToBackend' => true,
'enableUrlDecodeCache' => true,
'enableUrlEncodeCache' => true,
'emptyUrlReturnValue' => '/mysite/',
),
'pagePath' =>
array (
'type' => 'user',
'userFunc' => 'EXT:realurl/class.tx_realurl_advanced.php:&tx_realurl_advanced->main',
'spaceCharacter' => '-',
'languageGetVar' => 'L',
'rootpage_id' => '1',
'firstHitPathCache'=> '1',
),
'preVars' =>
array (
0 =>
array (
'GETvar' => 'L',
'valueMap' =>
array (
'cs' => '1',
),
'noMatch' => 'bypass',
),
),
'fixedPostVars' => array(
'19' => array(
array(
'GETvar' => 'tx_news_pi1[controller]',
'noMatch' => 'bypass',
),
array(
'GETvar' => 'tx_news_pi1[action]',
'noMatch' => 'bypass',
),
array(
'GETvar' => 'tx_news_pi1[news]',
'lookUpTable' => array(
'table' =>
'tx_news_domain_model_news',
'id_field' => 'uid',
'alias_field' => 'title',
'addWhereClause' => ' AND NOT deleted',
'useUniqueCache' => 1,
'useUniqueCache_conf' => array(
'strtolower' => 1,
'spaceCharacter' => '-',
),
'enable404forInvalidAlias' => '1',
'languageGetVar' => 'L',
'languageExceptionUids' => '',
'languageField' => 'sys_language_uid',
'transOrigPointerField' => 'l10n_parent',
),
),
),
),
),
);
php typo3 realurl
asked Jan 20 '14 at 19:01
David Apltauer
3831820
Just a word of advice, don't use CMS if you are building a custom app. I have found that making a CMS yield to your will is a lot harder than just building from scratch. CMS are good for simple sites; but if you are trying to build something with some advanced functionality, you should just build from scratch.
– user1477388
Jan 20 '14 at 19:05
I totally disagree to build anything from scratch, especially if you are working alone. One man can not implement security like TYPO3 security team, or Symfony, or Zend. There is no need to invent wheel, unless it is a better wheel :) and one man can hardly do it on his own.
– smitrovic
Feb 11 '15 at 11:01
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I managed to make news (tx_news) work realurl under the default language. Then I wanted to localize the news, so I created transaltions for them. However when I access the list view for a non-default language, it fails with
Request parameters could not be validated (&cHash comparison failed)
The failing link does not contain cHash, it looks like this
http://host.com/mysite/en/about-us/
What could be the cause and how to fix it? Here is the realURL setup
$GLOBALS['TYPO3_CONF_VARS']['EXTCONF']['realurl']=array (
'_DEFAULT' =>
array (
'init' =>
array (
'enableCHashCache' => true,
'enableCHashCache' => 1,
'respectSimulateStaticURLs' => 0,
'appendMissingSlash' => 'ifNotFile,redirect',
//'adminJumpToBackend' => true,
'enableUrlDecodeCache' => true,
'enableUrlEncodeCache' => true,
'emptyUrlReturnValue' => '/mysite/',
),
'pagePath' =>
array (
'type' => 'user',
'userFunc' => 'EXT:realurl/class.tx_realurl_advanced.php:&tx_realurl_advanced->main',
'spaceCharacter' => '-',
'languageGetVar' => 'L',
'rootpage_id' => '1',
'firstHitPathCache'=> '1',
),
'preVars' =>
array (
0 =>
array (
'GETvar' => 'L',
'valueMap' =>
array (
'cs' => '1',
),
'noMatch' => 'bypass',
),
),
'fixedPostVars' => array(
'19' => array(
array(
'GETvar' => 'tx_news_pi1[controller]',
'noMatch' => 'bypass',
),
array(
'GETvar' => 'tx_news_pi1[action]',
'noMatch' => 'bypass',
),
array(
'GETvar' => 'tx_news_pi1[news]',
'lookUpTable' => array(
'table' =>
'tx_news_domain_model_news',
'id_field' => 'uid',
'alias_field' => 'title',
'addWhereClause' => ' AND NOT deleted',
'useUniqueCache' => 1,
'useUniqueCache_conf' => array(
'strtolower' => 1,
'spaceCharacter' => '-',
),
'enable404forInvalidAlias' => '1',
'languageGetVar' => 'L',
'languageExceptionUids' => '',
'languageField' => 'sys_language_uid',
'transOrigPointerField' => 'l10n_parent',
),
),
),
),
),
);
php typo3 realurl
asked Jan 20 '14 at 19:01
David Apltauer
3831820
I managed to make news (tx_news) work realurl under the default language. Then I wanted to localize the news, so I created transaltions for them. However when I access the list view for a non-default language, it fails with
Request parameters could not be validated (&cHash comparison failed)
The failing link does not contain cHash, it looks like this
http://host.com/mysite/en/about-us/
What could be the cause and how to fix it? Here is the realURL setup
$GLOBALS['TYPO3_CONF_VARS']['EXTCONF']['realurl']=array (
'_DEFAULT' =>
array (
'init' =>
array (
'enableCHashCache' => true,
'enableCHashCache' => 1,
'respectSimulateStaticURLs' => 0,
'appendMissingSlash' => 'ifNotFile,redirect',
//'adminJumpToBackend' => true,
'enableUrlDecodeCache' => true,
'enableUrlEncodeCache' => true,
'emptyUrlReturnValue' => '/mysite/',
),
'pagePath' =>
array (
'type' => 'user',
'userFunc' => 'EXT:realurl/class.tx_realurl_advanced.php:&tx_realurl_advanced->main',
'spaceCharacter' => '-',
'languageGetVar' => 'L',
'rootpage_id' => '1',
'firstHitPathCache'=> '1',
),
'preVars' =>
array (
0 =>
array (
'GETvar' => 'L',
'valueMap' =>
array (
'cs' => '1',
),
'noMatch' => 'bypass',
),
),
'fixedPostVars' => array(
'19' => array(
array(
'GETvar' => 'tx_news_pi1[controller]',
'noMatch' => 'bypass',
),
array(
'GETvar' => 'tx_news_pi1[action]',
'noMatch' => 'bypass',
),
array(
'GETvar' => 'tx_news_pi1[news]',
'lookUpTable' => array(
'table' =>
'tx_news_domain_model_news',
'id_field' => 'uid',
'alias_field' => 'title',
'addWhereClause' => ' AND NOT deleted',
'useUniqueCache' => 1,
'useUniqueCache_conf' => array(
'strtolower' => 1,
'spaceCharacter' => '-',
),
'enable404forInvalidAlias' => '1',
'languageGetVar' => 'L',
'languageExceptionUids' => '',
'languageField' => 'sys_language_uid',
'transOrigPointerField' => 'l10n_parent',
),
),
),
),
),
);
php typo3 realurl
php typo3 realurl
asked Jan 20 '14 at 19:01
David Apltauer
3831820
asked Jan 20 '14 at 19:01
David Apltauer
3831820
asked Jan 20 '14 at 19:01
David Apltauer
3831820
asked Jan 20 '14 at 19:01
David Apltauer
3831820
asked Jan 20 '14 at 19:01
David Apltauer
3831820
3831820
Just a word of advice, don't use CMS if you are building a custom app. I have found that making a CMS yield to your will is a lot harder than just building from scratch. CMS are good for simple sites; but if you are trying to build something with some advanced functionality, you should just build from scratch.
– user1477388
Jan 20 '14 at 19:05
I totally disagree to build anything from scratch, especially if you are working alone. One man can not implement security like TYPO3 security team, or Symfony, or Zend. There is no need to invent wheel, unless it is a better wheel :) and one man can hardly do it on his own.
– smitrovic
Feb 11 '15 at 11:01
add a comment |
Just a word of advice, don't use CMS if you are building a custom app. I have found that making a CMS yield to your will is a lot harder than just building from scratch. CMS are good for simple sites; but if you are trying to build something with some advanced functionality, you should just build from scratch.
– user1477388
Jan 20 '14 at 19:05
I totally disagree to build anything from scratch, especially if you are working alone. One man can not implement security like TYPO3 security team, or Symfony, or Zend. There is no need to invent wheel, unless it is a better wheel :) and one man can hardly do it on his own.
– smitrovic
Feb 11 '15 at 11:01
Just a word of advice, don't use CMS if you are building a custom app. I have found that making a CMS yield to your will is a lot harder than just building from scratch. CMS are good for simple sites; but if you are trying to build something with some advanced functionality, you should just build from scratch.
– user1477388
Jan 20 '14 at 19:05
Just a word of advice, don't use CMS if you are building a custom app. I have found that making a CMS yield to your will is a lot harder than just building from scratch. CMS are good for simple sites; but if you are trying to build something with some advanced functionality, you should just build from scratch.
– user1477388
Jan 20 '14 at 19:05
I totally disagree to build anything from scratch, especially if you are working alone. One man can not implement security like TYPO3 security team, or Symfony, or Zend. There is no need to invent wheel, unless it is a better wheel :) and one man can hardly do it on his own.
– smitrovic
Feb 11 '15 at 11:01
I totally disagree to build anything from scratch, especially if you are working alone. One man can not implement security like TYPO3 security team, or Symfony, or Zend. There is no need to invent wheel, unless it is a better wheel :) and one man can hardly do it on his own.
– smitrovic
Feb 11 '15 at 11:01
add a comment |
4 Answers
4
active
oldest
votes
up vote
10
down vote
With this error I had fight a lot.
Go to Typo3 Install Tool => All configuration and change the value 1 => 0 for this attribute.
[FE] [pageNotFoundOnCHashError] = 0
I hope this gona solve the problem !!!
answered Jun 6 '14 at 5:46
Jimit Shah
518512
1
Perfect! you save my time @Jimit thanks :)
– Ghanshyam Gohel
Apr 11 '15 at 18:44
great, this does work but does it lower security ?
– webMan
Aug 9 '17 at 8:08
@webMan: yes , it decrease security , it helps at up-gradation of TYPO3.
– Jimit Shah
Aug 10 '17 at 10:23
add a comment |
up vote
2
down vote
I seem to have fixed it by emptying the tx_realurl_chashcache in the database.
answered Jan 20 '14 at 19:33
David Apltauer
3831820
this is the right answer, if you disable [FE] [pageNotFoundOnCHashError] you will no longer have a check by typo3 and security will be also an issue. the newer databes does not support this tablename. i emptying al of that.
– webfacer
Jul 13 at 17:32
add a comment |
up vote
1
down vote
I had to disable caching for the page. On my site it seems the "no_cache" parameter is confusing the chash calculation. This way i can keep the - i think important - security setting [FE][pageNotFoundOnCHashError] = 0
answered Nov 17 '16 at 11:03
InforMedic
11314
add a comment |
up vote
0
down vote
In Typo3 8.x version:
click the "Speaking Urls" module in the backend and than do "Flush all entries"
Now when you browse the frontend those entries would get re-created. And every thing should work fine.
Basically here we are deleting all page path entries for all pages so that they get created again.
Also you may delete the entries for the selected page by selecting the option "Delete all entries for this page"
answered Nov 11 at 8:09
Vikram
11
add a comment |
4 Answers
4
active
oldest
votes
4 Answers
4
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
10
down vote
With this error I had fight a lot.
Go to Typo3 Install Tool => All configuration and change the value 1 => 0 for this attribute.
[FE] [pageNotFoundOnCHashError] = 0
I hope this gona solve the problem !!!
answered Jun 6 '14 at 5:46
Jimit Shah
518512
1
Perfect! you save my time @Jimit thanks :)
– Ghanshyam Gohel
Apr 11 '15 at 18:44
great, this does work but does it lower security ?
– webMan
Aug 9 '17 at 8:08
@webMan: yes , it decrease security , it helps at up-gradation of TYPO3.
– Jimit Shah
Aug 10 '17 at 10:23
add a comment |
up vote
10
down vote
With this error I had fight a lot.
Go to Typo3 Install Tool => All configuration and change the value 1 => 0 for this attribute.
[FE] [pageNotFoundOnCHashError] = 0
I hope this gona solve the problem !!!
answered Jun 6 '14 at 5:46
Jimit Shah
518512
1
Perfect! you save my time @Jimit thanks :)
– Ghanshyam Gohel
Apr 11 '15 at 18:44
great, this does work but does it lower security ?
– webMan
Aug 9 '17 at 8:08
@webMan: yes , it decrease security , it helps at up-gradation of TYPO3.
– Jimit Shah
Aug 10 '17 at 10:23
add a comment |
up vote
10
down vote
up vote
10
down vote
With this error I had fight a lot.
Go to Typo3 Install Tool => All configuration and change the value 1 => 0 for this attribute.
[FE] [pageNotFoundOnCHashError] = 0
I hope this gona solve the problem !!!
answered Jun 6 '14 at 5:46
Jimit Shah
518512
With this error I had fight a lot.
Go to Typo3 Install Tool => All configuration and change the value 1 => 0 for this attribute.
[FE] [pageNotFoundOnCHashError] = 0
I hope this gona solve the problem !!!
answered Jun 6 '14 at 5:46
Jimit Shah
518512
answered Jun 6 '14 at 5:46
Jimit Shah
518512
answered Jun 6 '14 at 5:46
Jimit Shah
518512
answered Jun 6 '14 at 5:46
Jimit Shah
518512
518512
1
Perfect! you save my time @Jimit thanks :)
– Ghanshyam Gohel
Apr 11 '15 at 18:44
great, this does work but does it lower security ?
– webMan
Aug 9 '17 at 8:08
@webMan: yes , it decrease security , it helps at up-gradation of TYPO3.
– Jimit Shah
Aug 10 '17 at 10:23
add a comment |
1
Perfect! you save my time @Jimit thanks :)
– Ghanshyam Gohel
Apr 11 '15 at 18:44
great, this does work but does it lower security ?
– webMan
Aug 9 '17 at 8:08
@webMan: yes , it decrease security , it helps at up-gradation of TYPO3.
– Jimit Shah
Aug 10 '17 at 10:23
1
1
Perfect! you save my time @Jimit thanks :)
– Ghanshyam Gohel
Apr 11 '15 at 18:44
Perfect! you save my time @Jimit thanks :)
– Ghanshyam Gohel
Apr 11 '15 at 18:44
great, this does work but does it lower security ?
– webMan
Aug 9 '17 at 8:08
great, this does work but does it lower security ?
– webMan
Aug 9 '17 at 8:08
@webMan: yes , it decrease security , it helps at up-gradation of TYPO3.
– Jimit Shah
Aug 10 '17 at 10:23
@webMan: yes , it decrease security , it helps at up-gradation of TYPO3.
– Jimit Shah
Aug 10 '17 at 10:23
add a comment |
up vote
2
down vote
I seem to have fixed it by emptying the tx_realurl_chashcache in the database.
answered Jan 20 '14 at 19:33
David Apltauer
3831820
this is the right answer, if you disable [FE] [pageNotFoundOnCHashError] you will no longer have a check by typo3 and security will be also an issue. the newer databes does not support this tablename. i emptying al of that.
– webfacer
Jul 13 at 17:32
add a comment |
up vote
2
down vote
I seem to have fixed it by emptying the tx_realurl_chashcache in the database.
answered Jan 20 '14 at 19:33
David Apltauer
3831820
this is the right answer, if you disable [FE] [pageNotFoundOnCHashError] you will no longer have a check by typo3 and security will be also an issue. the newer databes does not support this tablename. i emptying al of that.
– webfacer
Jul 13 at 17:32
add a comment |
up vote
2
down vote
up vote
2
down vote
I seem to have fixed it by emptying the tx_realurl_chashcache in the database.
answered Jan 20 '14 at 19:33
David Apltauer
3831820
I seem to have fixed it by emptying the tx_realurl_chashcache in the database.
answered Jan 20 '14 at 19:33
David Apltauer
3831820
answered Jan 20 '14 at 19:33
David Apltauer
3831820
answered Jan 20 '14 at 19:33
David Apltauer
3831820
answered Jan 20 '14 at 19:33
David Apltauer
3831820
3831820
this is the right answer, if you disable [FE] [pageNotFoundOnCHashError] you will no longer have a check by typo3 and security will be also an issue. the newer databes does not support this tablename. i emptying al of that.
– webfacer
Jul 13 at 17:32
add a comment |
this is the right answer, if you disable [FE] [pageNotFoundOnCHashError] you will no longer have a check by typo3 and security will be also an issue. the newer databes does not support this tablename. i emptying al of that.
– webfacer
Jul 13 at 17:32
this is the right answer, if you disable [FE] [pageNotFoundOnCHashError] you will no longer have a check by typo3 and security will be also an issue. the newer databes does not support this tablename. i emptying al of that.
– webfacer
Jul 13 at 17:32
this is the right answer, if you disable [FE] [pageNotFoundOnCHashError] you will no longer have a check by typo3 and security will be also an issue. the newer databes does not support this tablename. i emptying al of that.
– webfacer
Jul 13 at 17:32
add a comment |
up vote
1
down vote
I had to disable caching for the page. On my site it seems the "no_cache" parameter is confusing the chash calculation. This way i can keep the - i think important - security setting [FE][pageNotFoundOnCHashError] = 0
answered Nov 17 '16 at 11:03
InforMedic
11314
add a comment |
up vote
1
down vote
I had to disable caching for the page. On my site it seems the "no_cache" parameter is confusing the chash calculation. This way i can keep the - i think important - security setting [FE][pageNotFoundOnCHashError] = 0
answered Nov 17 '16 at 11:03
InforMedic
11314
add a comment |
up vote
1
down vote
up vote
1
down vote
I had to disable caching for the page. On my site it seems the "no_cache" parameter is confusing the chash calculation. This way i can keep the - i think important - security setting [FE][pageNotFoundOnCHashError] = 0
answered Nov 17 '16 at 11:03
InforMedic
11314
I had to disable caching for the page. On my site it seems the "no_cache" parameter is confusing the chash calculation. This way i can keep the - i think important - security setting [FE][pageNotFoundOnCHashError] = 0
answered Nov 17 '16 at 11:03
InforMedic
11314
answered Nov 17 '16 at 11:03
InforMedic
11314
answered Nov 17 '16 at 11:03
InforMedic
11314
answered Nov 17 '16 at 11:03
InforMedic
11314
11314
add a comment |
add a comment |
up vote
0
down vote
In Typo3 8.x version:
click the "Speaking Urls" module in the backend and than do "Flush all entries"
Now when you browse the frontend those entries would get re-created. And every thing should work fine.
Basically here we are deleting all page path entries for all pages so that they get created again.
Also you may delete the entries for the selected page by selecting the option "Delete all entries for this page"
answered Nov 11 at 8:09
Vikram
11
add a comment |
up vote
0
down vote
In Typo3 8.x version:
click the "Speaking Urls" module in the backend and than do "Flush all entries"
Now when you browse the frontend those entries would get re-created. And every thing should work fine.
Basically here we are deleting all page path entries for all pages so that they get created again.
Also you may delete the entries for the selected page by selecting the option "Delete all entries for this page"
answered Nov 11 at 8:09
Vikram
11
add a comment |
up vote
0
down vote
up vote
0
down vote
In Typo3 8.x version:
click the "Speaking Urls" module in the backend and than do "Flush all entries"
Now when you browse the frontend those entries would get re-created. And every thing should work fine.
Basically here we are deleting all page path entries for all pages so that they get created again.
Also you may delete the entries for the selected page by selecting the option "Delete all entries for this page"
answered Nov 11 at 8:09
Vikram
11
In Typo3 8.x version:
click the "Speaking Urls" module in the backend and than do "Flush all entries"
Now when you browse the frontend those entries would get re-created. And every thing should work fine.
Basically here we are deleting all page path entries for all pages so that they get created again.
Also you may delete the entries for the selected page by selecting the option "Delete all entries for this page"
answered Nov 11 at 8:09
Vikram
11
answered Nov 11 at 8:09
Vikram
11
answered Nov 11 at 8:09
Vikram
11
answered Nov 11 at 8:09
Vikram
11
11
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f21242017%2fnews-realurl-i18n-in-typo3-chash-error%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Just a word of advice, don't use CMS if you are building a custom app. I have found that making a CMS yield to your will is a lot harder than just building from scratch. CMS are good for simple sites; but if you are trying to build something with some advanced functionality, you should just build from scratch.
– user1477388
Jan 20 '14 at 19:05
I totally disagree to build anything from scratch, especially if you are working alone. One man can not implement security like TYPO3 security team, or Symfony, or Zend. There is no need to invent wheel, unless it is a better wheel :) and one man can hardly do it on his own.
– smitrovic
Feb 11 '15 at 11:01