search

joshp23 / YOURLS-Expiry

YOURLS plugin to define conditions under which links will expire - time and click limited links
GNU General Public License v3.0
35 stars 13 forks source link

Keywords Randomised in Table #33

Closed lmizz92 closed 3 years ago

lmizz92 commented 3 years ago

Hi,

I have encountered an issue when adding a time counter to new links since on the YOURLS admin interface is for example "testing", in the keyword field in the expiry table is "0x74657374000000000000000000000000000". I have dropped the table and reinstalled the table and disabled other plugins to see if they effecting, but to no avail, keyword kept being a couple of numbers followed by a lot zeros. No errors are displayed when adding with debug set to true, therefore the link never expires and still is accessible after expiration.

What might be causing this pls?

Currently using YOURLS ver 1.8.1 and Expiry plugin ver 2.4.1

joshp23 commented 3 years ago

To clarify, you are attempting to add a Clock type expiry to a link via the admin area and the resulting value in the Timer column of the expiry table appears as 0x74657374000000000000000000000000000. You have tried to drop the database and the behavior remains. Is that right?

lmizz92 commented 3 years ago

Not exactly. I have these columns in the expiry table (keyword | type | click | timestamp | shelflife | postexpire) and the keyword column is being filled up with 0x74657374000000000000000000000000000, therefore if there is a column with the specific name of "Timer", it is not being created. I have tried dropping the expiry table and creating it again but the same issue occurs.

image

lmizz92 commented 3 years ago

Is there an update regarding this? What could be causing this, please?

joshp23 commented 3 years ago

I have been busy with my 9 to 5 and have not had an.opportunity to look into this. I might have some time this weekend to see if I can reproduce the error.

lmizz92 commented 3 years ago

I have been busy with my 9 to 5 and have not had an.opportunity to look into this. I might have some time this weekend to see if I can reproduce the error.

Thanks very much for the response back. Appreciated.

Omniru commented 3 years ago

This may be the same issue: https://github.com/joshp23/YOURLS-Expiry/issues/35#issuecomment-861717223

lmizz92 commented 3 years ago

Hi @Omniru,

Thanks for the thread, I was able to solve the issue.

Regards