vanxan / mollify

Automatically exported from code.google.com/p/mollify
0 stars 0 forks source link

Share Plugin, error on expirationdate #489

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. create new "share" with entered expiration date
2. version: 2.2.2 or 2.2.3
3.

the debuglog(mollify) the last 5 rows:

expiration:20131031111356, active:1, restriction:{type:pw, value:}}SERVICE 
(ShareServices)ServiceException: INVALID_REQUEST=Invalid ShareServices request: 
PUT share/38E80C581D9249CD976381C5D47A5324 Invalid datatype: 
expiration{0:{file:D:\apache24\htdocs\mollify\test2\backend\plugin\Share\ShareSe
rvices.class.php, line:102, function:invalidRequestException, 
class:ServicesBase, type:->, args:{0:Invalid datatype: expiration}}, 
1:{file:D:\apache24\htdocs\mollify\test2\backend\include\services\ServicesBase.c
lass.php, line:56, function:processPut, class:ShareServices, type:->, args:{}}, 
2:{file:D:\apache24\htdocs\mollify\test2\backend\include\MollifyBackend.class.ph
p, line:82, function:processRequest, class:ServicesBase, type:->, args:{}}, 
3:{file:D:\apache24\htdocs\mollify\test2\backend\r.php, line:63, 
function:processRequest, class:MollifyBackend, type:->, 
args:{0:Request}}}RESPONSE error {0:101, 1:Invalid request, 2:403} Invalid 
ShareServices request: PUT share/38E80C581D9249CD976381C5D47A5324 Invalid 
datatype: expiration

Invalid Datatype? what can i do?
Please help we need this feature.

regards,
Karsten

Original issue reported on code.google.com by karsten....@googlemail.com on 30 Oct 2013 at 9:30

GoogleCodeExporter commented 8 years ago
Fixed in 2.2.4.

Original comment by samuli.j...@gmail.com on 30 Oct 2013 at 11:49

GoogleCodeExporter commented 8 years ago
oh, thank you.
i see i can download it. 
thanks again.

regards,
karsten

Original comment by karsten....@googlemail.com on 30 Oct 2013 at 12:02

GoogleCodeExporter commented 8 years ago
one little thing.
the datepicker says the correct date and time
e.g.
2013/10/30 15:00:00 PM

but the database entry is -1 hour
e.g.
20131030160000

what i'm doing wrong?

Original comment by karsten....@googlemail.com on 30 Oct 2013 at 2:36

GoogleCodeExporter commented 8 years ago
oh, +1 hour :-)

Original comment by karsten....@googlemail.com on 30 Oct 2013 at 2:52

GoogleCodeExporter commented 8 years ago
I've noticed this at some point, but forgot to look into it. I suspect this is 
timezone issue, ie. the datepicker uses UTC and it is translated to current 
timezone. Or something like this, I'll check this out.

Original comment by samuli.j...@gmail.com on 30 Oct 2013 at 3:42

GoogleCodeExporter commented 8 years ago
thanks

Original comment by karsten....@googlemail.com on 30 Oct 2013 at 3:51

GoogleCodeExporter commented 8 years ago
Could you try version 2.2.6 
(https://code.google.com/p/mollify/downloads/detail?name=mollify_2.2.6.zip)?

I've been testing this for a while, and it seems to work now, but I'd like know 
how it works on others.

Original comment by samuli.j...@gmail.com on 31 Oct 2013 at 6:30

GoogleCodeExporter commented 8 years ago
it works perfectly.
thanks a lot.
i will send you a mail.

regards

Original comment by karsten....@googlemail.com on 4 Nov 2013 at 2:46