Forum Replies Created

Viewing 11 replies - 1 through 11 (of 11 total)
  • Plugin Author keith_wp

    (@keith_wp)

    No worries, appreciate the kind words and I’m happy it’s useful.

    I’m not a big WPCLI user either, but it comes into its own for anything you repeatedly do with WP – add the right chain of commands into a short script, and it’ll make those jobs a lot quicker and less error prone.

    Plugin Author keith_wp

    (@keith_wp)

    I never got around to adding sort options, so it doesn’t change anything from the default ordering of posts that WP returns (by published date).

    I’m guessing your “next post” was actually published before the “previous post”? Try manually setting the date in the affected posts and see if that’s better.

    Plugin Author keith_wp

    (@keith_wp)

    I’ve just checked and it still works fine on 8.1 (and maybe?? even from 7.4 when class property typing was introduced) – I’ve just upped the version number to be safe if/when I use some of the new 8.3 features and not realise it.

    Plugin Author keith_wp

    (@keith_wp)

    Thanks, forgot my dev box was stuck on 8.1… I’ve updated to 8.3 and fixed the deprecation warnings in the 0.4.4 release.

    Plugin Author keith_wp

    (@keith_wp)

    I’ve updated the plugin to at least stop breaking a site when it fails, and also made the regex a bit more robust – honestly, I’d be at a loss to make it any more generic; so if it fails now, it’s likely for a different reason I haven’t thought of yet.

    Plugin Author keith_wp

    (@keith_wp)

    If you’re getting that message, then SP isn’t putting the “fake” field into the login form and so any entry is something to be rejected.

    Which version of WP are you using? Or do you have any other fields on the login page? This plugin relies on a regex to alter the HTML and if that fails, it’ll break.

    I’ll update this and release a version where if it does fail, it will at least not break the form…

    Plugin Author keith_wp

    (@keith_wp)

    Probably not; if you’re getting that message, then SP isn’t putting the “fake” field in and treating any entry as something to be rejected.

    Looking at your form field list it’s probably due to the regex expecting the default registration fields and failing there. Are you using a plugin to add the extra fields or doing it by hand?

    Plugin Author keith_wp

    (@keith_wp)

    Automatic – as soon as you activate the plugin, it’ll add those extra columns to the User screen.

    Depending on what else you’ve got going on in the backend, you can either move/hide/widen columns within an existing plugin/functions.php or use my “Adjust Users Screen” plugin to do so.

    (Sorry for late reply, I don’t check here often enough.)

    Thread Starter keith_wp

    (@keith_wp)

    Re. not saving the ingredient measurements when adding a new recipe: I’ve checked now and it is because I added custom units. As they’ve been stored in the db options with carriage returns as the separator and update_post_meta() doesn’t do any trimming, they don’t subsequently match any of themselves again.

    In meta_box.php, I’ve changed:
    if ($new && $new != $old) {
    update_post_meta($post_id, $field['id'], $new);

    to quickly trim measurements:
    if ($new && $new != $old) {
    if ('ingredient' == $field['id']) foreach ($new as &$ingredient) $ingredient['measurement'] = rtrim($ingredient['measurement']);
    update_post_meta($post_id, $field['id'], $new);

    but it’d probably be better handled when saving the custom units initially.

    Also, http://ww.wp.xz.cn/extend/plugins/lightbox-plus/ has been working very nicely with the instruction images – I can now flip through a mini gallery of full size photos per recipe. Now I just need to take better photos 🙂

    Thread Starter keith_wp

    (@keith_wp)

    No worries – it is still a dev release after all.

    A couple of other things:

    • typo on line 19 of output.php – “Yeild”
    • and I can’t save Measurements on the initial post save; that may be because I added a few custom measurements in the options? I’ll check tomorrow.
    • You’ll be pleased to know that uncommenting the image per instruction bits in meta_box.php almost works right away:
    • the table is now too wide for the edit template – adding “float:left” to the “Upload Image” button is a quick fix for my screen width at least
    • it saves the post ID of the media library image, not the src so on line 234 you’ll need something like:
      if($row['image']) { $src = wp_get_attachment_image_src( $row['image'], 'thumbnail' ); echo $src[0]; }
    • and likewise on the frontend side in functions.php, something like:
      $output .= '<li style="clear:right">';
      if (isset($instruction['image']) AND is_numeric($instruction['image'])) {
      $src = wp_get_attachment_image_src( $instruction['image'], 'thumbnail' );
      $output.= '<img style="float:right;margin-bottom:10px" src="'.$src[0].'" width="'.$src[1].'" height="'.$src[2].'" alt="" />';
      }
      $output .= $instruction['description'].'
    • ‘;
      in the instructions loop, although preferably a bit less quick’n’dirty 🙂 I also needed to add “clear:right” to the #recipress_recipe .recipe-taxes style…

    Another thought/feature request – using something like soundex to determine that something like “carrot” and “carrots” are the same ingredient?

    Nixanadoo,

    I had a similar (if not identical) problem on that page – I was using quotes in the alt text/title for an image and they weren’t appearing in the form fields when managing a gallery after adding them.

    The bug fix for this is to open up admin/manage-images.php and change line 354 from:
    <input name="alttext[<?php echo $pid ?>]" type="text" style="width:95%; margin-bottom: 2px;" value="<?php echo stripslashes($picture->alttext) ?>" />

    to:
    <input name="alttext[<?php echo $pid ?>]" type="text" style="width:95%; margin-bottom: 2px;" value="<?php echo htmlentities(stripslashes($picture->alttext)) ?>" />

    (In other words, add at least the htmlentities() function to any text that can get displayed between hardcoded quotes etc, in this case the value=”” bit.)

Viewing 11 replies - 1 through 11 (of 11 total)