tag:wedge.org,2012-03-16:recentWedge - Bug reports2024-03-19T03:26:11ZLive information from Wedge
Wedge
WedgeRe: Possible bug with custom fieldsI'm so out of the loop anyway. Yesterday I spent a few hours rewriting the audio player for my very old prog-rock website (fox.noisen.com), which isn't running on Wedge but is running an old version of Aeva Media (it's the website I actually wrote the 'Foxy' module for, hence the name), and ended up getting it to work on modern browsers. Then I wondered to myself, is it worth porting over to Aeva and/or Wedge..? I don't know. I have this weird feeling that Foxprog is the only website to use the playlist features of Aeva Media, anyway.]]>Naohttps://wedge.org/profile/Nao/2020-04-06T14:54:31Z2020-04-06T14:54:31Ztag:wedge.org,2020-04-06:msg-297949Re: Possible bug with custom fields And I did not send anything to the repo. This was on AeMe on SMF, so I have no idea if the code is even valid for Wedge.]]>live627https://wedge.org/profile/live627/2020-01-10T22:58:39Z2020-01-10T22:58:39Ztag:wedge.org,2020-01-10:msg-297947Re: Possible bug with custom fields;) You could just as well post a PR..? Or maybe there's one... I must admit, I don't check the git page often.
(As a quick note: I believe the custom field feature for AeMe was written by Dragooon originally, so I'm probably not well versed in it.)]]>Naohttps://wedge.org/profile/Nao/2019-05-11T11:36:51Z2019-05-11T11:36:51Ztag:wedge.org,2019-05-11:msg-297932Possible bug with custom fields
Create a custom field in the gallery
Make it a checklist
Make it required
Make it searchable
Edit an item, don't fill that field
Observe errors when saving
Code: [Select]// Add them to the form foreach ($fields as $field) { -if ($field['type'] == 'checkbox') +if ($field['type'] == 'checkbox' && empty($field['searchable'])) $field['value'] = explode(', ', $field['value']);
+ // JTR: preparsecode() corrupts the array by converting it to a string. +if (isset($_POST['custom_field'][$field['id']]) && !is_array($_POST['custom_field'][$field['id']])) -preparsecode($value); +preparsecode($value);
// Do the value checks if ($field['type'] == 'checkbox') { -foreach ($value as $val) -if (!in_array($val, $field['options'])) -fatal_error(sprintf($txt['aeva_cf_invalid'], $field['name'])); - // Nothing set? if (empty($value) && $field['required']) fatal_error(sprintf($txt['aeva_cf_empty'], $field['name'])); elseif (empty($value)) continue;
+foreach ($value as $val) +if (!in_array($val, $field['options'])) +fatal_error(sprintf($txt['aeva_cf_invalid'], $field['name'])); + // Set the proper value $value = implode(', ', $value); }
]]>live627https://wedge.org/profile/live627/2019-01-31T23:54:24Z2019-01-31T23:54:24Ztag:wedge.org,2019-01-31:msg-297927Re: Error id_file in Media GalleryTo be specific, the problem was caused by Aeva Media's transparency lookup when someone was uploading an embedded video (e.g. YouTube, Dailymotion...) It hadn't happened in years here, so I had no way to know lol.
Also used the opportunity to fix the same bug in AeMe 2.x, and released 2.11 for AeMe users. And yes, that includes the infamous installation bug fix... (Not that it'll help users who already had the bug. I told them how to fix it.)]]>Naohttps://wedge.org/profile/Nao/2017-07-25T16:21:45Z2017-07-25T16:21:45Ztag:wedge.org,2017-07-25:msg-297751