zikula-modules / Clip

Flexible Document Creator
35 stars 8 forks source link

After Zikula Update to 1.3.9 build12, no edit possible #162

Open trichers opened 10 years ago

trichers commented 10 years ago

I updated to from Zikula 1.3.6 to 1.3.9 build12 and now I can´t edit Clip-publications. The follling message is coming: WARN (4): E_WARNING: readdir() expects parameter 1 to be resource, boolean given in User.php Zeile 53 WARN (4): E_WARNING: readdir() expects parameter 1 to be resource, boolean given in User.php Zeile 53 WARN (4): E_WARNING: readdir() expects parameter 1 to be resource, boolean given in User.php Zeile 53 WARN (4): E_WARNING: readdir() expects parameter 1 to be resource, boolean given in User.php Zeile 53 WARN (4): E_WARNING: readdir() expects parameter 1 to be resource, boolean given in User.php Zeile 53 WARN (4): E_WARNING: readdir() expects parameter 1 to be resource, boolean given in User.php Zeile 53 WARN (4): E_WARNING: readdir() expects parameter 1 to be resource, boolean given in User.php Zeile 53 WARN (4): E_WARNING: readdir() expects parameter 1 to be resource, boolean given in User.php Zeile 53 WARN (4): E_WARNING: readdir() expects parameter 1 to be resource, boolean given in User.php Zeile 53 WARN (4): E_WARNING: readdir() expects parameter 1 to be resource, boolean given in User.php Zeile 53 WARN (4): E_WARNING: readdir() expects parameter 1 to be resource, boolean given in User.php Zeile 53 WARN (4): E_WARNING: readdir() expects parameter 1 to be resource, boolean given in User.php Zeile 53 WARN (4): E_WARNING: readdir() expects parameter 1 to be resource, boolean given in User.php Zeile 53 WARN (4): E_WARNING: readdir() expects parameter 1 to be resource, boolean given in User.php Zeile 53 WARN (4): E_WARNING: readdir() expects parameter 1 to be resource, boolean given in User.php Zeile 53 WARN (4): E_WARNING: readdir() expects parameter 1 to be resource, boolean given in User.php Zeile 53 WARN (4): E_WARNING: readdir() expects parameter 1 to be resource, boolean given in User.php Zeile 53 WARN (4): E_WARNING: readdir() expects parameter 1 to be resource, boolean given in User.php Zeile 53 WARN (4): E_WARNING: readdir() expects parameter 1 to be resource, boolean given in User.php Zeile 53 ....

espaan commented 10 years ago

is there also info on which User.php the message is coming from ? In Clip branch 0.9 there is no readdir in Controller/User.php or Api/User.php

trichers commented 10 years ago

no, that makes it so difficult to find the mistake.

espaan commented 10 years ago

Weird. I searched with phpstorm in my local 139 test site in modules and system and no readdir comes to light with a boolean or something around line 53.

trichers commented 10 years ago

Did you also search in the Clip-files?

espaan commented 10 years ago

Yes certainly. But I searched in the current github 0.9 branch, what version are you using ?

porzellankompass commented 10 years ago

I think the problem concerns the new user.php. After upgrading to 1.3.9 safety edition my so long defined and well functioning Clip Filters on a local machine did the following u.a.: WARN (4): E_WARNING: urlencode() expects parameter 1 to be string, array given in User.php Zeile 869 I tested it for boolean also; relations and lists seem not to be affected. System is using Wamp Apache 2.2.22, php 5.3.13, sql 5.5.24

espaan commented 10 years ago

And with new user.php you mean which one ? From Clip itself ?

porzellankompass commented 10 years ago

I would like to maintain a discussion in core: A temporary solution could be: https://github.com/zikula/core/issues/1952

We did some changes in modules/Clip/lib/Clip/Api/User.php

So mattheo should concern to start his new Clip version earlier. How could I help?

porzellankompass commented 10 years ago

Ok, it seems to be a Clip problem. Let us have mattheo a new Clip Version.

trichers commented 10 years ago

I´ve made a new installation of Zikula 1.3.9 with Clip 0.9.3 and imported the Clip publicationtypes. Now the edit works fine. So, Clip 0.9.3 works fine with 1.3.9 The mistake must be a part of the update process?!