Forum Replies Created

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

    (@i4nd90)

    1. The main issue is tabindex is getting set to -1, which is a problem when the loaded items are links. This takes the first one out of the tab flow which means it becomes inaccessible to keyboard users after the focus is moved away. With regards to setting focusVisible:false, it is a semantic way of removing the outline (since a browser stylesheet looks a bit like this: :focus-visible { outline: auto 1px -webkit-focus-ring-color }). In my case I had an issue reported to me that the first item in each ajax load had a different background. The item had focus-visible styling, but because the outline had been stripped off, it made no sense visually. focusVisible:false is a consistent solution, and essentially creates an invisible pointer for accessible users to take off from again.
    2. If the first page is preloaded using the add-on, then the first ajax load needs to account for this and trigger the moveFocus() function
    Thread Starter i4nd90

    (@i4nd90)

    Thanks so much @jarnovos and @rogierlankhors

    To be honest it’s been hard for me to replicate too, issues have been intermittent.

    When the updated version is shipped I will test on our development server and get back to you.

    Thread Starter i4nd90

    (@i4nd90)

    Nice one, thanks

    Having the same issue with Gutenberg Editor. I want to use the default gallery interface to easily select my images, and then use this great-looking plugin to make it look nice and add a lightbox.

    When I use the [gallery] shortcode and associated attributes it works as expected. If I don’t, the gallery block displays as if this plugin wasn’t installed.

    Is this plugin designed to work with blocks?

    Thanks

    Thread Starter i4nd90

    (@i4nd90)

    Thanks, have done.

    Thread Starter i4nd90

    (@i4nd90)

    Sure, I’d prefer not to make the screenshots public, how is best to show them to you?

    Thread Starter i4nd90

    (@i4nd90)

    Thanks, I have just tried while leaving the find and replace blank, and actually the issue is exactly the same – so it’s actually the automated replacement causing the issue and the search/replace was being ignored.

    Plugin Author i4nd90

    (@i4nd90)

    Hi there

    As a follow up, you’re better off just adding the ‘https://’ in the URL within the event, not here in the template. Also beware – from the code above you’re missing crucial wrapping quotations around the href attribute.

    Ian

    Plugin Author i4nd90

    (@i4nd90)

    Hi Nadja

    I’m not quite sure what you mean when you say the year calendar on the left. Anyway, using the configuration options it is possible to show all events from one year in a list, the basic premise of which is below:

    HTML template:

    <div class="clndr-controls">
      <div class="current-month">
        <%= intervalStart.format("YYYY") %>
      </div>
      <div class="clndr-nav clndr-clearfix">
        <div class="clndr-previous-button">?</div>
        <div class="clndr-next-button">?</div>
      </div>
    </div>
    
    <div class="event-listing">
      <div class="event-listing-title">Events</div>
      <% _.each(eventsThisInterval, function(interval) { %>
        <% _.each(interval, function(event) { %>
          <div>
            <span class="event-item-date">
              <% if (event.end != event.start) {
                startMY = moment(event.start).format("MM YY");
                endMY = moment(event.end).format("MM YY");
                if (startMY === endMY) { %>
                  <%= moment(event.start).format("D") %>–<%= moment(event.end).format("D MMMM") %>
                <% } else { %>
                  <%= moment(event.start).format("D MMMM") %> – <%= moment(event.end).format("D MMMM") %>
                <% }
              } else {  %>
                <%= moment(event.start).format("D MMMM") %>
              <% } %>
            </span>
            <span class="event-item-name"><%= event.title %></span>
            <% if (event.time) {  %>
              <span class="event-item-time"><%= event.time %></span>
            <% } %>
            <% if (event.desc) {  %>
              <span class="event-item-desc"><%= event.desc %></span>
            <% } %>
          </div>
          <% }); 
        }); %>
    </div>

    JS Options:

    lengthOfTime: {
      months: 12,
      interval: 12,
      startDate: moment().startOf('year')
    }

    This excludes any kind of calendar grid because I can’t see how it’s necessary in a year view. Anyway, I hope this proof of concepts helps somewhat with what you want to do and you’re able to modify it to suit you. Obviously you’ll need to play around with the CSS to make this look presentable for each instance you’re implementing.

    In regards to greying out past events, this would simply be a conditional statement on each event’s date in comparison to today, and for example, adding a class or style to the event information holder div which changes its appearance.

    Cheers

    Ian

    Plugin Author i4nd90

    (@i4nd90)

    Hi Claudia

    I have just tested with 4.8.2 and couldn’t seem to replicate your issue. What OS and browser are you using? It could be a conflict with another plugin, I suggest perhaps temporarily isolating this plugin to see if the problem still exists.

    Ian

    Plugin Author i4nd90

    (@i4nd90)

    Sorry, no support for recurring events at the moment. Apologies I cannot be of more help! Might try and add event duplication at some point but I won’t be able to do this any time soon I’m afraid.

    Plugin Author i4nd90

    (@i4nd90)

    Sure, just go to the instance you are using, and in the HTML template change where it says <a target="_blank" to <a target="_self".

    I’ve also just published an update (1.04) where you can set the link target individually for each event. After updating, you’ll have access to the variable url_target in the instance’s HTML template.

    Plugin Author i4nd90

    (@i4nd90)

    Thanks for the information.

    There’s something going on in your environment that’s causing the issue, I think.

    What’s happening is that the CLNDR.js script is looking to utilise any already loaded dependencies, and in your case thinks it’s found a Node/CommonJS/Browserify loading method to hook into. However when it uses require to bring in jQuery and Moment.js, this fails. Without looking into the specifics of your environment it’s hard for me to know why.

    Also this seems more like an issue with CLNDR.js itself over the plugin. It might be worth seeing if the issue is replicated in an implementation outside of WordPress – my hunch is that it will. In this case you’ll be better off opening an issue on the project’s Git unless you’re able to identify why this is happening specifically on your server.

    Sorry I can’t be of more help!

    Plugin Author i4nd90

    (@i4nd90)

    Hi there

    I am successfully running the plugin without any errors on a fresh install of 4.7.4.

    Could you please dump the list of your activated plugins so I can see if there are any potential conflicts? Also – what environment are you on? WordPress.com or self-hosted?

    Ian

    Forum: Plugins
    In reply to: [Event CLNDR] Past Events
    Plugin Author i4nd90

    (@i4nd90)

    There were some more instance options added in version 1.0.2 which means you no longer need to do this manually. You can just check the boxes to show your choice or past/present/future events.

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