Work started on 5.3.3


#6

Great:+1 @pulsecms :
And again a request:
The new feature {{recentposts_visual: "3": "blog / subblog": "true": "150"}} is great and I like to use it. But if I have ## more ## before the 150 characters are over, that will not be translated. Can this be changed so that ## more ## works in this variant as well?
Screenshot_2019-05-09%20Hallo%20und%20willkommen
(Maybe that has already wished someone else, then sorry for duplicate entries)
Many Thanks
Annett


Pulse 5.3.3 is here! 🚀
#7

Good point Annett.

To add to this @pulsecms, could the cut off take into account the last word. At the moment, it counts the characters and chops at exactly that length. This needs to be done a little more thoughtfully, so that you don't end up with half words. For instance:

Consider 'The quick brown fox jumps over the lazy dog'

If a limit of 36 was specified, the output would be 'The quick brown fox jumps over the la' which makes no sense.

If the 36th character sits within a word, then if should truncate the word that is cut, so that it would display as 'The quick brown fox jumps over the...' If this brings the actual character count below the length threshold, that's fine - At least the output would be clean.


#8

Absolute :+1:. You're right @ezchile . The function of ## more ## could be the same in recentpost as in the "correct" blog preview.
I always stumble over pasted {{gal: ...}} tags, which are then truncated in plain text ... :upside_down_face:


#9

Thanks for those - have noted your 1 and 2 for a future update, but not at this time :slight_smile: But makes sense so will bear in mind for a release soon.

That's because it's evolved since version 5.0 and "power" features were meant to be in there - as not all users require these features. That said, we're already considering to move some items around so thanks for this feedback. Again though, won't be 5.3.3 but will bear in mind for a version down the road.


#10

Good thinking @annett and @ezchile - I think we can add word-wrap to the truncation in recentposts_visual and also somehow exclude readmore or other tags.

We'll see what we can do for this time :slight_smile:

Also - please note the great new read more add-on by @IvaRo


#11

Another wish:
if I have a video in the Media folder and click on it starts video immediately. Is it possible to open videos like pictures so that I can see and copy the link - for embedding? Maybe add a title tag - for the future ...?
Many Thanks


New Release: 5.3.5
#12

And again me... @pulsecms
It goes back to recent_visual and galleries (had the problem ever addressed - sorry - it is not resolved):
I have a gallery {{gal: testgalery2: 1: yes}} at the beginning of a blog post (save me the featured image).
On my homepage I load this post.
But in the frontend, I can not handle the gallery properly ...

I've seen through everything, my source code is clean and structured. I upload the same gallery via blog show or directly to the page everything works perfectly. I think it is not a mistake of mine.
To make it clear that the problem lies in the recent_posts tag, I've created a few simple test pages - the title says the content.

https://www.junge-blogger.oggym.de/test-with-gal-only
{{gal: testgalery2: 1: yes}} (works)

https://www.junge-blogger.oggym.de/test-with-blog-show-and-gal
{{blog-show: test2: [[blog-contentloop (<< blog-item-author >> << blog-item-date >> << blog-item-title >> << blog-item-content >> )]]}} (is working)

https://www.junge-blogger.oggym.de/test-with-gal-in-recentpost
{{recentposts_visual: "3": "blog / test2": "true": "150"}} (does not work)

https://www.junge-blogger.oggym.de/test-with-picture
{{recentposts_visual: "3": "blog / test3": "true": "150"}} (works)

I'm not able to figure out exactly where the error lies - I've already looked at everything. It would be really great if I could use recent_post with gallery at the beginning. These functions give a very nice overview on a start page - certainly not only for me ...
Many Thanks
Annett


#13

This has been added for the next release @annett & @ezchile

  • Truncation is now based on number of words
  • Also with {{recentposts_visual}} tag it now strips pulse tags from a string - also removes ##more##

Word count had some odd edge cases around punctuation. HTML is stripped, but Pulse tags aren't. Now has been all improved. Thanks for the feedback!


#14

So just to be clear...

  • the page here is not working
  • the issue is you are using the {{gal: testgalery2: 1: yes} in a blog post and the gallery is not showing in the blog post?

Let me know


#15

This can be done a future version also, thanks


#16

Hi Michael, that is great news. Thanks.


#17

@pulsecms, thats great, thank you. :smiley:


#18

Hi @michael,
sorry for that - the link works perfect for me. But OK. :woman_shrugging:
Please try this:

  • open a blog post
  • put {{gal: gallery1: 1: yes}} first
  • open pages-> home and add
    {{recentposts_visual: "3": "blog": "true": "150"}}
  • please test the gallery
    I used the Original Pulse 532 templates, nothing changed.
    Maybe it's not meant to work - but it would be fine for me.
    Please excuse the circumstances.
    Many Thanks
    Annett

#19

Thanks @annett - that workflow example is really helpful and can replicate this - we'll look into this :slight_smile:


#20

Thanks @annett: I've retested and {{gal: gallery1: 1: yes}} and it is now being filtered out in the recent posts visual output (as per above - Work started on 5.3.3 changes).

@ezchile That missing "/" was a tricky one.

The url filtering was removing leading slashes in the blog item image extraction code. This is now improved.

Also, the displayed image in the recent post visual items have a max width of 100%, so that should be preserving the aspect ratio.


#21

Thank you, @pulsecms. This is great news and I am looking forward to the next version.


#22

That's great. Thanks @pulsecms


#23

Based on a great request by @ezchile (and others), we've got the Featured Image selector for Blog posts wired up.

Preview of how this is looking :star_struck:

Ref:


Recent post visual
#24

Looks great! Can't wait to try this!!


#25

Hello everyone.
I have some ideas for improving Pulse.

  1. Use the SSL Certificate for Start Pages and Administrator.
  2. List of installed add-ons in the administrator.
  3. Add translations for "show more" and "show less" blocks.
  4. How do I view the Pulse tag on a page, such as: {{tagname: var1: var2: var3}}?
  5. Manual in every Pulsexx.zip installation package.
  1. If you install Pulse in a subdirectory or subdomain, the pages will also appear in an unsecured "http" format. I tried to add redirect to htaccess = failed. I also tried to add redirects to meta headers. The page was redirected, the problem was with cookies and especially when viewing the page from the administrator / preview.
    I solved it by adding meta tag to layout.php and admin index.php (maybe login.php).
    // meta tag
    <meta http-equiv = "Content-Security-Policy" content = "upgrade-insecure-requirements">
    Link to page: "https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/upgrade-insecure-requests".

In install.php, enter an option to install the pulse in the ssl secure mode.

In the admin / security panel, add an option that will allow "Content-Security-Policy".

  1. Man is an observant being and does not remember all pulse commands to insert pulse marks.
    You enter the help in admin / index.php, in the tag header behind the log, enter the drop-down list of installed plugins. At this point, the list will still be available - visible.

  2. Add language translations for blocks, such as "show more" and "show less".
    Put these extensions into the Pulse installation. If you are interested, I will send you a Pulse extension.

  3. How to display Pulse tags / code correctly? For example, you need to include a code example in the manual. Pulse still accepts this as a command.

  4. The best way to keep the current pulse guide is to create a Pulse layout and directly in the Pulse installation package. This cannot be a problem for Pulse creators because they will only update once for the current installation package.
    Do not use a PDF file for this purpose.
    Do not insert an impulse pulse introduction in this manual. Who bought Pulse has already read it in large manuals (pdf).
    The great advantage of this guide is:
    a) You still have a current guide.
    b) You have one block for each category.
    c) Translation - Manual: Use Google Chrome, open block in admin, right click = option: translate page. That's it, you have a translated manual, be sure to save it.
    d) You can enter your ideas, enhancements, notes, and examples from this forum into this manual.
    DETERMINE that each user deserves such a guide !!!
    Maybe it was a good idea to distribute this guide into two separate folders.
    The current manual and what's new in Pulse, so the user can add information to his manual.