slamorte

It goes well. There is an free open-source community maintained version of this service. It’s more geared towards developers than the public.

https://github.com/humanmade/S3-Uploads

Reverting to 6.4.1 solved the issue.

If you have command line access enter the following:

wp plugin auto-updates disable modern-events-calendar-lite
wp plugin delete modern-events-calendar-lite
wp plugin install modern-events-calendar-lite --version=6.4.1 --activate

Your event data will not be affected.

• This reply was modified 4 years, 2 months ago by slamorte.
• This reply was modified 4 years, 2 months ago by slamorte.

We have the same issue.

As far as I can tell, Captivate Sync uses its own non-standard post edit screen. This means there’s no way to extend the Captivate post type with custom taxonomies, ACF fields, custom metadata, and so on. Plugins like The SEO Framework and Yoast will also not work in post edit as designed.

This is super limiting as far as customizing the post type. It means we can’t use your plugin at all and it’s causing us to re-evaluate Captivate as our plugin host. If we wanted to integrate WordPress to Captivate we’d need to rewrite a plugin or API integration from scratch.

The solution for this plugin is for it to use a standard WordPress post edit screen with Captivate’s custom fields added. This would allow developers to properly extend your post type with ACF, custom taxonomies, plugins, and so on.

We have the same issue — no attributes are added at all. Our theme does filter the content, but even after removing our custom filters, this plugin is not adding attributes.

Hi,

Still having an issue with styling.

I’ve put two ALM buttons on my page for you to look at, each pulling a different template (we bought the template folder upgrade).

First ALM

The first one uses a shortcode to call a simple repeater template that does not add one row per three content items, and uses your CSS to override the Foundation floats.

Shortcode

[ajax_load_more theme_repeater="load-more-stories.php" post_type="trnn_story" offset="13" posts_per_page="12" pause="true" scroll="false" destroy_after="36" css_classes="row" button_label="See more stories ≫"]

Template:

<div class="medium-4 columns norow">

   <?php if ( has_post_thumbnail() ) { ?>
   <a href="<?php the_permalink(); ?>"><?php the_post_thumbnail('block');?></a>
   <?php } ?>

   <?php echo the_terms( $post->ID, 'topics', '<div class="labels">',' ','</div>' ) ?>

   <a href="<?php the_permalink(); ?>"><h3><?php the_title(); ?></h3></a>

   <?php echo wp_trim_words( get_the_excerpt(), 20);?>

</div>

CSS

.alm-reveal {
  .medium-4.columns.norow {
    display: inline-block;
    float: none;
    padding-bottom: 20px;
    vertical-align: top;
    width: 33%;
  }
}

The problem here is that even with your styling addition only two of the medium-4 content items appear per ‘row’, unless I also override Foundations width setting (add “width=33%;” to the CSS). However if I manually set the width I get unwanted results on other screen sizes — it overrules Foundation’s responsiveness. Essentially the position of the second content item shift slightly when changing from float: left to display: inline-block.

Second ALM

The second one uses a shortcode to call the repeater that adds one row per three content items and uses the default Foundation styling.

<?php if($alm_item%3 == 1){echo '<div class="row">';} ?>

<div class="medium-4 columns">

  <?php if ( has_post_thumbnail() ) { ?>
    <a href="<?php the_permalink(); ?>"><?php the_post_thumbnail('block');?></a>
    <?php }  ?>

    <?php echo the_terms( $post->ID, 'topics', '<div class="labels">',' ','</div>' ) ?>

    <a href="<?php the_permalink(); ?>"><h3><?php the_title(); ?></h3></a>

    <?php echo wp_trim_words( get_the_excerpt(), 20);?>

  </div>

  <?php if($alm_item%3 == 0){ echo '</div>'; } ?>

The styling here is great and fully Foundation. The problem is the Load More button is “done” after the first press. You said “Sometimes when a template is not opened and closed with an HTML element the plugin gets confused,” so I also wrapped the repeater in another div element but it didn’t help.

Website is here and login available on request.