Forum Replies Created

Viewing 15 replies - 1 through 15 (of 15 total)
  • Thread Starter steacha

    (@steacha)

    Thanks, I submitted my report there. Any chance you could look at it soon or provide a way to debug this?

    Thread Starter steacha

    (@steacha)

    Ok, well I solved my problem.

    In line 2517 in core.php, the custom marker is extracted with the following function call:

    $icon = wp_get_attachment_image_src( get_post_thumbnail_id( $postID ));

    This will return the ‘thumbnail’ size that is configured within WordPress (in Settings > Media). This ‘thumbnail’ dimension applies to ALL thumbnails that WP automatically generates for all uploaded images. It can be anything and NOT necessarily match the size of the custom markers.

    The fix is easy, though. Just change the line to the following:

    $icon = wp_get_attachment_image_src( get_post_thumbnail_id( $postID ), “full” );

    This way, WP is forced to send the ORIGINAL size of the image. I think you should consider adding this fix to the plugin, Ian. Or, at least, a parameter to the shortcode to instruct the plugin to use custom sizes or WP-generated ‘thumbnail’ dimensions.

    Thread Starter steacha

    (@steacha)

    I did read this thread, actually.

    And, the icon links look like this for me:

    <path to uploads directory>/marker-image.png-150×150.png

    No resize is in the URL. I am not using JetPack or Photon.

    Thread Starter steacha

    (@steacha)

    I sort of assumed I would have to change the plugin code itself, but yes, a hook might make life easier (I’ve never used one, but I am thinking it cannot possibly be hard to implement).

    Thread Starter steacha

    (@steacha)

    My apologies, I meant to also mention that ALL_CUSTOM would indeed do the trick (as opposed to the other ones, thanks for clarifying), but somehow forgot because I wanted to expand on the formatting.

    In any case, thanks for considering this, David, but for the time being where in the code would I need to make my PHP modifications to do what I explained earlier (displaying all custom fields as opposed to naming them directly in the template)?

    Thread Starter steacha

    (@steacha)

    I am thinking that ALL_IPTC, ALL_EXIF and ALL_PDF would not work because they would contain information in addition to the custom fields, correct? But, in this scenario, the custom fields are the only ones needed.

    Would the following work for formatting?

    <div class="custom_field">
      <div class="name">custom field name</div>
      <div class="value">custom field value</div>
    </div>

    Or even better:

    <dl class="custom_field">
      <dt class="name">custom field name</dt>
      <dd class="value">custom field value</dd>
    </dl>

    [Moderator Note: Please post code & markup between backticks or use the code button. Your posted code may now have been permanently damaged by the forum’s parser.]

    Thread Starter steacha

    (@steacha)

    Thanks for the answer, David.

    I was reading through many posts involving PHP coding that I wondered where indeed would be the right place to make a modification requiring me to display all the custom fields created for a library item without having to explicitly name them using the [+custom:my_custom_field_name+] notation in the template.

    Thread Starter steacha

    (@steacha)

    Thanks David, this is really cool and more straightforward than I thought! again, great work.

    Thread Starter steacha

    (@steacha)

    Lrrr, thank you for your comments, you do raise a few interesting points.

    Also, thanks for the info, David.

    Thread Starter steacha

    (@steacha)

    Hi David,

    Thank you for investigating this so promptly and for your update. Your solution seems very promising, I have another question:

    I was thinking of having each gallery (on the same page) be contained within their own ‘slide container’ such that when say page 2 is clicked on gallery 1, a sliding effect takes place to reveal the 2nd page of gallery 1 without gallery 2 and 3 being affected.

    Do you see this scenario adding much more complexity to the solution you’re proposing?

    I ran into the same issue and fixed it by adding the data-height line in the widget() function, to the Like Box definition:

    ...
    data-width="<?php echo $this->facebook_width; ?>"
    data-height="<my height>"
    ...

    Just downloaded this plugin and ran into the same limitation. I assumed it was added since this was mentioned about 5 months ago. Any quick fix to add the functionality?

    Thread Starter steacha

    (@steacha)

    I’ve managed to resolve the issue with the headlines and post dates now showing. That was due to a faulty CSS rule which caused their opacity to be set to zero.

    Now I have to figure out the rest.

    steacha

    (@steacha)

    This plugin is great, but I am running into 2 little problems which I hope someone can help me solve:

    1) My post headlines are not shown.

    2) My post publish dates are not shown

    3) My post contents are not appearing on the timeline either

    4) How do I make the timeline start at the end (or current event)? start_at_end=”true” seems to have no effect

    Only the featured images for each post are shown. Also, is it possible to have the headlines link to the actual post itself? I’m in a little bit of a time rush, it would be cool and much appreciated if someone could assist me with this quickly. ??

    Thread Starter steacha

    (@steacha)

    I think the 404 problems were due to a typo in my .htaccess. But now that I’ve fixed it, every time I try to add a French translation for my posts and click “Edit”, I get the following error:

    “You attempted to edit an item that doesn’t exist. Perhaps it was deleted?”

    Any help debugging this would be much appreciated.

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