Posts by: juergen

Posts: 1480
Post: 11542
Topic: without Home

Also, how to get rid of

@We are sorry, but this site is now blocked for editing by another user.[…]

Typesetter CMS does not support simultaneous editing of content by multiple admins. It is therefore recommended that you always log out after editing so that another user can log in immediately.

You can delete /data/_lock_[random hash] files on you webhost (via S/FTP or other direct file system access) to get rid of leftover admin sessions.

 

9 months ago
Post: 11537
Topic: YouTube Embed proposal to upgrade

Youtube plugin for ckeditor is not bad either

Sure. both have their pros and cons.
In general, using dedicated section types suits my designs better, but sometimes an inline solution is the way to go.

though rather unknown.

Unknown? Um ... it actually ranks place 4 on all non-standard-build CKE plugins (out of over 300)
I'd rather call that one of the most popular.

9 months ago
Post: 11534
Topic: YouTube Embed proposal to upgrade

1st merge is done - we're ver. 1.0-b4 now.

Mind forking?

9 months ago
Post: 11533
Topic: YouTube Embed proposal to upgrade

You do not have 'YouTube Embed' on GitHub

Now I have

Maybe, it will be interesting for you.

Sure. Async loading was overdue. Awesome!

I'll merge versions short-time… be back.

9 months ago
Post: 11531
Topic: SimpleBlog upgrade

The solution proposed by Jürgen can be used to upgrade Simple_Blog to version 3.5 and can be uploaded to the Typesetter site so it can be used by everyone.

[…] but i must say that the arrows of the details - summary - version make a better impression. This should be done - evtl. colored arrows - before publishing a new version [...]

When making plugins that deal with dynamically created content, one of the harder decisions always is, how much default front-end style and user experience behavior it should come with.

I personally prefer as-lean-as-possible solutions that …
  A) can still be easily overruled via custom CSS and
  B) use as little as possible JavaScript for client-side behavior, which can be hard or even impossible to modify, once initiated.

When it comes to SimpleBlog, there are a few things in the markup that should be improved for better styling possibilities and DOM manipulation.
The problem is, SimpleBlog is very popular and any changes in the html output will cause issues with existing and custom styled installations, when the plugin gets the update.
That's why I always use customized versions, adapted for the current use case.

IMO SImpleBlog should in fact become part of Typesetter core. This would allow much better (Bootstrap) integration and interoperability with other plugins.
But that's nothing done in a few hours, at least not for me.

 

Edited: 9 months ago
Post: 11526
Topic: SimpleBlog upgrade

Hi florin and mabu

if I understand the question right and you wish to make all archive gadget levels collapsible and collapsed by default, this is what I'd do.

This solution is for the original SimpleBlog (up to ver. 3.0.4) gadget markup structure, which looks like this:

<div class="simple_blog_gadget">
  <div>
    <span class="simple_blog_gadget_label">Archives</span>
    <ul>
      <li>
        <div class="simple_blog_gadget_year">2018</div>
        <ul>
          <li>
            <a class="blog_gadget_link">November (2)</a>
            <ul class="simple_blog_category_posts nodisplay">
              <li>
                <a href="/Blog/My-Post-1">My Post 1</a>
              </li>
              <li>
                <a href="/Blog/My-Post-2">My Post 2</a>
              </li>
            </ul>
          </li>
        </ul>
        </ul>
          <li>
            <a class="blog_gadget_link">December (1)</a>
            <ul class="simple_blog_category_posts nodisplay">
              <li>
                <a href="/Blog/My-Post-3">My Post 3</a>
              </li>
            </ul>
          </li>
        </ul>
      </li>
    </ul>
    <ul>
      <li>
        <div class="simple_blog_gadget_year">2019</div>
        <ul>
          <li>
            <a class="blog_gadget_link">January (1)</a>
            <ul class="simple_blog_category_posts nodisplay">
              <li>
                <a href="/Blog/My-Post-4">My Post 4</a>
              </li>
            </ul>
          </li>
        </ul>
      </li>
    </ul>
  </div>
</div>

This would be the jQuery Code:

$(function(){ // function call when DOM is ready, omit when using PHP $page->jQueryCode .= '…'; 

  $('.simple_blog_gadget ul ul').hide(); // initially hide all but the first level ULs 

  $('.simple_blog_gadget_year')
    .css('cursor', 'pointer')   // will be clickable, so let's change the cursor to pointer 
    .on('click', function(){    // click handler
      $(this).siblings('ul').slideToggle();
    })
    .find('.blog_gadget_link')
      .off('click') /* this will unbind the original click handler set by SimpleBlog, 
                     * will only work if this function is called later than SimpleBlog's
                     */
      .on('click', function(){
        $(this).siblings('ul').slideToggle();
      });

}); // closing of DOM ready function 

 

I hope it's still helpful.

Cheers,
Jürgen

9 months ago
Post: 11352
Topic: OnePageToolkit.gadgetconfig is undefined

I see that ver 2.0-b1 still needs some work...

Please download this patch and use the 3 included files to overwrite the ones in /addons/OnePageToolkit

Then click the 'Upgrade to version 2.0-b1.1' link on the Admin Management page.

 

Hope it will work now.

Edited: 1 year ago
Post: 11349
Topic: SEO improvement

To add a rel="nofollow noopener" attribute to all links that already have a target="_blank" attribute would be

PHP:

<?php
global $page;
$page->jQueryCode .= '$(\'a[target="_blank"]\').attr("rel", "nofollow noopener");';
?>

… or in existing JS:

$(function(){ $('a[target="_blank"]').attr("rel", "nofollow noopener"); });

But I'm uncertain if all crawlers will comply with a rule that is implemented subsequently via javascript. Googlebot most likely will.

Edited: 1 year ago
Post: 11347
Topic: SEO improvement

There is currently no way to add arbitrary attributes to menu items, but as a workaround we can add Extra Content Areas to menus (since Typesetter 5.1), so…

  1. Create an Extra Content Area via Admin Toolbar -> Content -> Extra Content. Use "Editable Text" and call it e.g. "Nofollow Menu Link"
  2. Edit the new Area using CK Editor Source view and add your link e.g.
    <a class="nav-link" href="[your link]" target="_blank" rel="nofollow noopener">[Your Link Label]</a>
    (the "nav-link" class is needed with Bootstrap 4 navs)
  3. Go to Page Manager and add a new item to the menu, choose "Extra Content" from the tabs at the top of the popup, select your "Nofollow Menu Link" Area.

This should do the trick.

Edited: 1 year ago
Post: 11343
Topic: OnePageToolkit.gadgetconfig is undefined

I'm sorry for the late reply.

I'm currently updating OPTK for Bootstrap 4 compatibility and improving some known issues.


Please get OnePageToolkit 2.0-b1

While ver 2.0 is a bit different on the programmatic side (OOP/autoloading), it looks and works almost the same as ver 1.x and should also be compatible with former installations.

Just replace everything in the /addons/OnePageToolkt directory with the contents of the new version. Then click the 'Upgrade to version 2.0-b1' link on the Admin Management page.

This version is not really tested yet. If you get any errors or have issues please post them here,
 

Edited: 1 year ago

News

elFinder 2.1.50 in Upcoming Release
12/28/2019

A new release for Typesetter is in the works with a lot of improvements including the ... Read More

Typesetter 5.1
8/12/2017

Typesetter 5.1 is now available for download. 5.1 includes bug fixes, UI/UX improvements, ... Read More

More News

HH-Support

Company located in Tórshavn, Faroe Islands. * Webpage Design * Consultant & Provider of a wide range of programs for visually impaired and dyslextics.

Find out more about our Provider Spotlight

Log In

  Register