Hi,
seems we have a problem with DMX 5.3.8. that we didn’t have with 5.2.7. Couldn’t find this yet in this forum:

We discovered that sometimes file uploads via WebDAV do not show up in notifications (subscription e-mails).

So I ran approx. 20 test, i.e. 20 uploads of different txt-files via WebDAV. After each upload I ran the service task. Each time the scheduler said: “Found 1 new events” BUT sent 0 notifications :-(
However, if I upload txt-files via Browser to the same folder, notification is sent.

Then I uploaded a folder containing 1 file, again via WebDAV. I am notified about the new folder, but not about the new file (which, however, is properly uploaded)!

We use a Total Commander WebDAV plugin.
I attached below the Total Commander protocol of a single file upload (WebDAVTestDok13.txt).

Any idea?

Best regards,
Mathias


=================
Get dir: /dmxdav.axd/root\test\Ordner am 7-10-11 per Webdav erstellt\
PROPFIND /dmxdav.axd/root/test/Ordner%20am%207-10-11%20per%20Webdav%20erstellt/ HTTP/1.1
Depth: 1
Content-Type: text/xml; charset="utf-8"
User-Agent: ezdavplugin
Host: www.tmf-ev.de
Content-Length: 0
Connection: Keep-Alive
Cache-Control: no-cache
Cookie: .DOTNETNUKE=; dmxdavcookie=
******Received headers
HTTP/1.1 207 Multi-Status
Cache-Control: private
Content-Length: 9053
Content-Type: text/xml
Server: Microsoft-IIS/7.5
X-DMXDav-Handled: True
X-AspNet-Version: 2.0.50727
MS-Author-Via: DAV
X-DMXDav-Version: 5.3.8.0
X-Powered-By: ASP.NET
Date: Fri, 07 Oct 2011 14:24:41 GMT
207 Multi-Status
=================
File send: /dmxdav.axd/root\test\Ordner am 7-10-11 per Webdav erstellt\WebDAVTestDok13.txt
Last upload step: Send actual file
PUT /dmxdav.axd/root/test/Ordner%20am%207-10-11%20per%20Webdav%20erstellt/WebDAVTestDok13.txt HTTP/1.1
Content-Type: application/octet-stream
Content-Length: 13
User-Agent: ezdavplugin
Host: www.tmf-ev.de
Connection: Keep-Alive
Cache-Control: no-cache
Cookie: .DOTNETNUKE=; dmxdavcookie=

******Received headers
HTTP/1.1 201 Created
Cache-Control: private
Content-Length: 0
Content-Type: text/html
Server: Microsoft-IIS/7.5
X-DMXDav-Handled: True
X-AspNet-Version: 2.0.50727
MS-Author-Via: DAV
X-DMXDav-Version: 5.3.8.0
X-Powered-By: ASP.NET
Date: Fri, 07 Oct 2011 14:24:41 GMT
201 Created
=================
Get dir: /dmxdav.axd/root\test\Ordner am 7-10-11 per Webdav erstellt
PROPFIND /dmxdav.axd/root/test/Ordner%20am%207-10-11%20per%20Webdav%20erstellt/ HTTP/1.1
Depth: 1
Content-Type: text/xml; charset="utf-8"
User-Agent: ezdavplugin
Host: www.tmf-ev.de
Content-Length: 0
Connection: Keep-Alive
Cache-Control: no-cache
Cookie: .DOTNETNUKE=; dmxdavcookie=

******Received headers
HTTP/1.1 207 Multi-Status
Cache-Control: private
Content-Length: 9804
Content-Type: text/xml
Server: Microsoft-IIS/7.5
X-DMXDav-Handled: True
X-AspNet-Version: 2.0.50727
MS-Author-Via: DAV
X-DMXDav-Version: 5.3.8.0
X-Powered-By: ASP.NET
Date: Fri, 07 Oct 2011 14:24:42 GMT
207 Multi-Status

Hi Mathias,

I have no clue why as the notification is not in the WebDAV component but embedded in the methods that do the actual editing/adding/etc. So it is the same code as the UI. Which means it is weird to have a discrepancy. You'll need to check the DMX_Log table first as it is the start for notification. If the edit/add doesn't appear in the log it won't send notifications.

Peter