Hi Aaron,
thanks for you reply. I checked this now. All resources are loaded and there is 
no match with "not_found" or something similar. I compared the direct connected 
version with the no direct connected and i found no difference. Any other idea? 
Does anyone uses DirectConnect and AjaxUpdateLinks?
Thomas

Am 27.05.2014 um 06:16 schrieb Aaron Rosenzweig <aa...@chatnbike.com>:

> Hi Thomas,
> 
> Make sure ALL of your resources are loading. Maybe there is something with 
> HTTP vs HTTPS or anything really…. When you went to direct connect something 
> else that is important may not be loading either.
> 
> Open up Safari and check that all resources are loaded in the resource 
> viewer. Also, do a “view source” and search for “not_found"
> AARON ROSENZWEIG / Chat 'n Bike
> e:  aa...@chatnbike.com  t:  (301) 956-2319
>       
> 
> On May 23, 2014, at 7:18 AM, Thomas Grass (01SoftwareSolutions) 
> <off...@01softwaresolutions.eu> wrote:
> 
>> Hi,
>> this is the first time i used WODirectConnect on our Testserver. 
>> 
>> Everything works fine but using a AjaxUpdateLink would give no result 
>> (clicking on a AjaxUpdateLink do just nothing). The Javascript-Console of my 
>> Chrome browser has the following Error-Report for me:
>> 
>> 
>>              • Uncaught TypeError: Cannot read property 'sub' of null 
>> wonder.js:350
>>              • AjaxUpdateLink._updatewonder.js:350
>>              • AjaxUpdateLink.updatewonder.js:345
>>              • onclick
>> 
>> The wonder.js on line 350 looks like this:
>> 
>>       _update: function(id, actionUrl, options, elementID, queryParams) {
>>              if (elementID) {
>>                      actionUrl = actionUrl.sub(/[^\/]+$/, elementID);       
>> //line nr 350
>>              }
>>              actionUrl = actionUrl.addQueryParameters(queryParams);
>>              if (options && options['_r']) {
>>                      actionUrl = actionUrl.addQueryParameters('_r='+ id);
>>              }
>>              else {
>>                      actionUrl = actionUrl.addQueryParameters('_u='+ id);
>>              }
>>              actionUrl = actionUrl.addQueryParameters(new Date().getTime());
>>              new Ajax.Updater(id, actionUrl, 
>> AjaxOptions.defaultOptions(options));
>>      }
>> 
>> 
>> The weird thing is: If I do not use WODirectConnect, the AjaxUpdateLink 
>> works. Also weird: All the other Ajax-Elements (like AjaxSubmitButton, 
>> AjaxUpdateContainer, AjaxObserveField etc.) works fine with or without 
>> WODirectConnect.
>> 
>> What did I miss?
>> 
>> Thomas
>> 
>> 
>> 
>> 
>> 
>> --
>> Thomas Grass, B.Sc. | 01SoftwareSolutions 
>> +49 (89) 41 41 41 03-0
>> off...@01softwaresolutions.eu | www.01softwaresolutions.eu
>> Lichtenbergstraße 8 | D-85748 Garching b München
>> 
>> 
>> _______________________________________________
>> Do not post admin requests to the list. They will be ignored.
>> Webobjects-dev mailing list      (Webobjects-dev@lists.apple.com)
>> Help/Unsubscribe/Update your Subscription:
>> https://lists.apple.com/mailman/options/webobjects-dev/aaron%40chatnbike.com
>> 
>> This email sent to aa...@chatnbike.com
> 

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Reply via email to