[Neos] TYPO3-Neos-1.1-Beta - exception

nikos nick at jamalade.com
Sat Apr 26 22:46:21 CEST 2014 

Hi Christian

I have applied the changes as in https://review.typo3.org/#/c/29667/, cleared caches, browser & server, but still the same problem only this time no 
exception is raised just in the backend get the following error message:

"Server communication error: Not Implemented"


The http request & response for clicking on "Raw Content" are shown below (this time using Firefox).
The webserver is Apache 2.2.26, PHP 5.3.28.


http request [
    PUT /neos/service/user-preferences HTTP/1.1
    Host: b2neos.rxrxxx.com
    User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:28.0) Gecko/20100101 Firefox/28.0
    Accept: */*
    Accept-Language: en-US,en;q=0.5
    Accept-Encoding: gzip, deflate
    Content-Type: application/x-www-form-urlencoded; charset=UTF-8
    X-Requested-With: XMLHttpRequest
    Referer: http://b2neos.rxrxxx.com/@user-nickp
    Content-Length: 93
    Cookie: __utma=75836182.1618492923.1297639486.1392322925.1394536449.216; 
__utmz=75836182.1355493336.195.53.utmcsr=google|utmccn=(organic)|utmcmd=organic|utmctr=(not%20provided); 
TYPO3_Flow_Session=XsJoLDnxUINcHvR52crKTDiFQh8RwPh6
    Connection: keep-alive
  ]
  http response [
    HTTP/1.1 501 Method Not Implemented
    Date: Sat, 26 Apr 2014 19:10:54 GMT
    Server: Apache
    X-Powered-By: PHP/5.3.28
    X-Flow-Powered: Flow/2.2
    Set-Cookie: TYPO3_Flow_Session=XsJoLDnxUINcHvR52crKTDiFQh8RwPh6; Path=/; HttpOnly
    Content-Length: 2
    Connection: close
    Content-Type: application/json
  ]


Many thanks for your help with this.

Nikos

On 26/04/2014 13:49, Christian Müller wrote:
> Hi Nikos,
>
> would you do me a favor and apply this change:
> https://review.typo3.org/#/c/29667/
>
> then clear all caches and try again?
> As you can see in my note this action should actually never be called so I have no idea what is happening. I would have suggested you modified the
> page rendering somehow but as you said the same error happens with the standard demo site that isn't the case.
>
> After looking at all the code I reread your very first post, thanks for adding the request headers, because they tell something odd there:
> GET /neos/service/user-preferences HTTP/1.1
>
> This should never be called and in fact is nowhere in our code. Actually it should be a PUT request. I guess you use the same browser for local
> testing and testing on your server? So probably not the browsers fault but the server. I also just tried with Safari (as you) and it works. So
> definitely something about the server not working with PUT requests. Can you post the server response headers for any request? Just to see what kind
> of webserver and version it is?
>
> Would like to hear the outcome.
>
> Thanks,
> Christian
>
> nikos wrote:
>> Hi Christian
>> Do you know where exactly the call to REST service is made? I've been
>> trying to debug the javascript to see what is happening but haven't
>> found anything yet :(
>>
>> On 26/04/2014 10:22, Christian Müller wrote:
>>> Hi Nikos,
>>>
>>> really difficult to debug, it misses a template but this template no
>>> longer exists, so I wonder why it tries to load it at all. The problem
>>> is I am
>>> not even sure when it was deleted. I will try to find out.
>>> Maybe something you could try is clear all your browser caches, local
>>> storage and cookies for the domain. I doubt it helps but you never
>>> know...
>>>> I tried Neos 1.1 beta2 hoping this might fix the problem but
>>>> unfortunately still have the same problem, also tried using the
>>>> NeosDemoSite :(
>>>> Template could not be loaded. I tried
>>>> "resource://TYPO3.Neos/Private/Templates/Service/UserPreference/Index.html"
>>>>
>>>> I have tested the same install on a standalone machine with has no issue
>>>> at all. Clearly a problem running on my Host but can't figure out what
>>>> is wrong? I guess this is related to moving away from EXTJS, if so does
>>>> anyone know of any configuration changes that may be required?
>>>>
>>>> My host is running PHP 5.3.28. There is no problem running with Neos
>>>> 1.0.2 .
>>>>
>>>>
>>>> On 25/04/2014 14:48, nikos wrote:
>>>>> Hi all
>>>>>
>>>>> I have installed the 1.1 Beta on my shared host after a successful run
>>>>> on my dev machine. I tar balled from my local install as access to
>>>>> command line
>>>>> on the host is by cron only which is a pain.
>>>>>
>>>>> I have cleared all the caches, started with a clean database and
>>>>> imported a site I am working on, which works fine in 1.0.2 (host & dev
>>>>> box)and Beta
>>>>> 1.1 (on dev box).
>>>>>
>>>>> Everything on the front end works fine and noticebly faster :) however
>>>>> when I try and make changes via the backend I get a communication error
>>>>> displayed (red pop up) with the following exception:
>>>>>
>>>>> Uncaught exception #1225709595 in line 222 of
>>>>> /home/rerootco/public_html/neos/TYPO3-Neos-1.1-Beta/Data/Temporary/Production/Cache/Code/Flow_Object_Classes/TYPO3_Fluid_View_TemplateView.php:
>>>>>
>>>>>
>>>>> Template could not be loaded. I tried
>>>>> "resource://TYPO3.Neos/Private/Templates/Service/UserPreference/Index.html"
>>>>>
>>>>>
>>>>>
>>>>> 16
>>>>> TYPO3\Fluid\View\TemplateView_Original::getTemplatePathAndFilename(NULL)
>>>>>
>>>>> 15 TYPO3\Fluid\View\TemplateView_Original::getTemplateIdentifier(NULL)
>>>>> 14 TYPO3\Fluid\View\AbstractTemplateView::render()
>>>>> 13
>>>>> TYPO3\Flow\Mvc\Controller\ActionController_Original::callActionMethod()
>>>>> 12
>>>>> TYPO3\Flow\Mvc\Controller\ActionController_Original::processRequest(TYPO3\Flow\Mvc\ActionRequest,
>>>>>
>>>>> TYPO3\Flow\Http\Response)
>>>>> 11
>>>>> TYPO3\Flow\Mvc\Dispatcher_Original::dispatch(TYPO3\Flow\Mvc\ActionRequest,
>>>>>
>>>>> TYPO3\Flow\Http\Response)
>>>>> 10 TYPO3\Flow\Mvc\Dispatcher::dispatch(TYPO3\Flow\Mvc\ActionRequest,
>>>>> TYPO3\Flow\Http\Response)
>>>>> 9 call_user_func_array(array|2|, array|2|)
>>>>> 8
>>>>> TYPO3\Flow\Mvc\Dispatcher::Flow_Aop_Proxy_invokeJoinPoint(TYPO3\Flow\Aop\JoinPoint)
>>>>>
>>>>>
>>>>> 7 TYPO3\Flow\Aop\Advice\AdviceChain::proceed(TYPO3\Flow\Aop\JoinPoint)
>>>>> 6
>>>>> TYPO3\Flow\Security\Aspect\RequestDispatchingAspect_Original::blockIllegalRequestsAndForwardToAuthenticationEntryPoints(TYPO3\Flow\Aop\JoinPoint)
>>>>>
>>>>>
>>>>> 5 TYPO3\Flow\Aop\Advice\AroundAdvice::invoke(TYPO3\Flow\Aop\JoinPoint)
>>>>> 4 TYPO3\Flow\Aop\Advice\AdviceChain::proceed(TYPO3\Flow\Aop\JoinPoint)
>>>>> 3 TYPO3\Flow\Mvc\Dispatcher::dispatch(TYPO3\Flow\Mvc\ActionRequest,
>>>>> TYPO3\Flow\Http\Response)
>>>>> 2 TYPO3\Flow\Http\RequestHandler::handleRequest()
>>>>> 1 TYPO3\Flow\Core\Bootstrap::run()
>>>>>
>>>>> HTTP REQUEST:
>>>>> GET /neos/service/user-preferences HTTP/1.1
>>>>> Content-Length: 96
>>>>> Content-Type: application/x-www-form-urlencoded; charset=UTF-8
>>>>> Accept: */*
>>>>> Accept-Encoding: gzip, deflate
>>>>> Accept-Language: en-us
>>>>> Connection: keep-alive
>>>>> Dnt: 1
>>>>> Host: bneos.mycom.com
>>>>> Origin: http://bneos.mycom.com
>>>>> Referer: http://bneos.mycom.com/@user-nickp
>>>>> User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_2)
>>>>> AppleWebKit/537.75.14 (KHTML, like Gecko) Version/7.0.3
>>>>> Safari/537.75.14
>>>>> X-Requested-With: XMLHttpRequest
>>>>>
>>>>> key=contentEditing.editPreviewMode&value=rawContent&__csrfToken=0ffb733d3c3cadd61396fc39d9c5bee6
>>>>>
>>>>>
>>>>>
>>>>> HTTP RESPONSE:
>>>>> [response was empty]
>>>>>
>>>>>
>>>>> Wondering if anyone has seen this before or has any ideas of how to
>>>>> rectify?
>>>>>
>>>>> Thanks
>>>>>
>>>>> Nick
>>>>
>>

More information about the Neos mailing list