TYPO3 Core

System: Debian Linux 3.2.0-4-amd64 #1 SMP Debian 3.2.57-3+deb7u1 x86_64
PHP-Version: 5.4.4-14+deb7u9
Webserver: Apache 2.2.22
OpCode Cache: There is an XCache Modul (Version 2.0.0). The cache has been initialized. A reload of the webserver did not change anything either.
Disabled PHP functions: pcntl_alarm pcntl_fork pcntl_waitpid pcntl_wait pcntl_wifexited pcntl_wifstopped pcntl_wifsignaled pcntl_wexitstatus pcntl_wtermsig pcntl_wstopsig pcntl_signal pcntl_signal_dispatch pcntl_get_last_error pcntl_strerror pcntl_sigprocmask pcntl_sigwaitinfo pcntl_sigtimedwait pcntl_exec pcntl_getpriority pcntl_setpriority

I also cleared the PHP opcode cache via install tool.

I can confirm this behaviour.

If you set in Core/Bootstrap.php $allowCaching to FALSE instead of TRUE (line 225)

public function loadConfigurationAndInitialize($allowCaching = FALSE, ...

it will work.

a function call with

\TYPO3\CMS\Core\Core\Bootstrap::getInstance()->loadConfigurationAndInitialize(FALSE, 'TYPO3\\CMS\\Core\\Package\\PackageManager');

will not help.

I've seen also the function annotation '@internal This is not a public API method, do not use in own extensions' ;) But how to build an eID Dispatcher without bootstrap??

Same here, I tried this: http://stackoverflow.com/questions/21139769/typo3-extbase-ajax-without-page-typenum

It works if I change allowCaching to TRUE as mentioned above.

public function loadConfigurationAndInitialize($allowCaching = FALSE, ...

But then, I had to change it back because I couldn't open the Install Tool (Lock Cache Error or smth.).

If I change the code in the dispatcher from

\TYPO3\CMS\Core\Core\Bootstrap::getInstance()->loadConfigurationAndInitialize

to

\TYPO3\CMS\Core\Core\Bootstrap::getInstance()

it works for me. Can someone confirm this?

Hi Klaus,
I can confirm that this

\TYPO3\CMS\Core\Core\Bootstrap::getInstance()

works!

Thank you very much.

By the way: I guess that the script which I am using is yours (Extbase Dispatcher for Ajax Calls TYPO3 6.1 namespaces from Klaus Heuer). If this is the case - why does it work without (...)->loadConfigurationAndInitialize? Are there any pitfalls omitting it?

And for the records:
There is a warning

PHP Warning: Invalid argument supplied for foreach() in /usr/local/share/php/typo3/typo3_src-6.2.3/typo3/sysext/core/Classes/Utility/RootlineUtility.php line 269

when the Dispatcher is called directly after clearing General and Frontend Cache. It occurs on

$TSFE->determineId();

But this is probably off topic.

Cheers
Dirk

Hi Dirk and all,

thank for confirmation - and yes, the script you mentioned is from me ;)

As far as see, there are not any pitfalls, but I didn't tested it in detail until now. However, some other things can be cleared up (e.g. a conect to DB is with 6.1/6.2 not neccessary as I understood) and maybe we have a chance to work now even with mapped tables - which failed in the past. But I think this will be offtopic here...

Adressed to Phillip:
I think we can close this here. But I'm still a litle bit wondering, than an eID Ajax dispatcher (which is widely used) not described in any core documents (as far as I know). Developers have to pick-it-up at stackoverflow or on private blogs but not in the typo3 docs. I'm not a core developer, I write extensions, but if someone with a 'core-background' can assist, my help is shure and maybe we have some days an proved, offical ajax eID solution ;)

PS: I'm not a ghostwriter here, I just didn't find a profil edit function to edit an last name;)

Greetings
Klaus

Hi Klaus, hi all,
thank you again for your quick assistance.
I would gladly help testing and improving your eID Ajax dispatcher solution.
I had to set it up in a number of projects and each time I had to search the internet for a solution.

My proposal:
Let's implement a working eID Ajax dispatcher as an extension. This extension could even be included as sys extension but not installed per default.

There is quite a good solution in pt_extbase already (which is running under TYPO3 v6.2). As far as I can see it consists in only two scripts. But I hesitate to use it in my projects since pt_extbase brings a lot more stuff (which can break).

Cheers
Dirk

Klaus no-lastname-given wrote:

I've seen also the function annotation '@internal This is not a public API method, do not use in own extensions' ;) But how to build an eID Dispatcher without bootstrap??

You don't do it ;)

Helmut Hummel wrote:

Klaus no-lastname-given wrote:

I've seen also the function annotation '@internal This is not a public API method, do not use in own extensions' ;) But how to build an eID Dispatcher without bootstrap??

You don't do it ;)

This annotation is not reflected in the public available API documentation under api.typo3.org (http://typo3.org/api/typo3cms/class_t_y_p_o3_1_1_c_m_s_1_1_core_1_1_core_1_1_bootstrap.html#a3967ec2bccd66f3a9de5bcb7ec32dee3). I.e. as a developer I will have to lookup each method in the source code... Umh!

Anyway - thank you all for digging into this and especially to Helmut for providing so much further information.
Cheers Dirk

Dirk Wenzel wrote:

This annotation is not reflected in the public available API documentation under api.typo3.org I.e. as a developer I will have to lookup each method in the source code... Umh!

I agree, that official API has to be documented better. We are getting better in that, but there is still a lot of legacy code where it is not clear, what is internal and what public API