Community Support for OpenDocMan (Deprecated)

I fresh installed OpenDocMan 1.2.6 daily update version in my localhost using with Xampp. Its working perfect.
But I found a problem in Admin Delete/Undelete page.

Undelete is not working in Admin. When i click Undelete this error is appearing.

-------------------------------------
Object not found!

The requested URL was not found on this server. The link on the referring page seems to be wrong or outdated. Please inform the author of that page about the error.

If you think this is a server error, please contact the webmaster.
Error 404
192.168.5.67
5/19/2011 8:28:00 AM
Apache/2.2.14 (Win32) DAV/2 mod_ssl/2.2.14 OpenSSL/0.9.8l mod_autoindex_color PHP/5.3.1 mod_apreq2-20090110/2.7.1 mod_perl/2.0.4 Perl/v5.10.1
-------------------------------------


When i was used 1.2.5.7 version there Undelete is worked.

Regards,
Shashi G Kiran.

Make sure your base_url config value in the Settings admin page is correct.

Hai Stephen. My base_url is correct. remaining all patths is opening correct. But Undelete action only am getting problem. If base_url problem means remaining all paths will be affected. But not. Where can I check specially Settings admin page.

My main opendocman URL & Settings Admin page base_url also same.

http://192.168.5.67/opendocman

Thank U.

Stephen Wrote:Make sure your base_url config value in the Settings admin page is correct.

I have this same problem. When try to undelete file I get:
The requested URL /vpr/out.php&last_message=message_document_has_been_archived was not found on this server.

Please help.

I experience this problem also. Base_url setting seems no problemo.
Kindly please help. Thanks.

I fixed a couple of issues in the Delete/Undelete tool yesterday. I will be pushing out a new release today that you can upgrade to (no database changes required). Hopefully it will resolve your issues.

I have downloaded 1.2.6.1 and the undelete works well now like a charm.
thank you very much mr. steven for your quick response, u've saved my day

Thanks Stephen,
The latest version of 1.2.6.1 solved this bug! We are happy here).
Thanks Milian