Closed rdhrkns closed 13 years ago
I think the problem is that you added a poll fieldtype to an existing channel. Then a bunch of errors were getting thrown cuz there were no poll options found. I think I fixed that in my latest commit: ae91be798189e8395bb104ca5b6cded788a91448
Tell me if this fixes the issue.
Just installed the 0.2Beta, but it does not solve the errors..
I didn't tag my latest commit. So if you just download the v0.2-beta it will not include the code I modified.
Oke, added the lines by hand, and the errors are gone. Then I added a test entry with just to awnsers, the errors appear again for the enty's not containing any poll data.
Addition to the above behavior. This is only present when logged in to the system
Quite weird. I made some changes in the latest commit (15d4c679a4aa4eca0d7d03a6a99614dfc9e51ee3). Try replacing all the files and see if you still get any errors.
No more errors now after replacing all the files.
Nice, thanks for pointing out this issue.
My field is called main_poll according my fieldgroupname_fieldname scheme.
I updated this naming in the tag example {...field_id="{main_poll:field_id}"...}, Then already when calling the site a bunch of php errors are thrown (http://www.tilburgdegekste.com/ee2/ )