Work started on 5.3.3


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


That's great. Thanks @pulsecms


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:


Recent post visual

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


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 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: "".

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.


Thanks @IvaRo

  1. It should be 100% SSL compatible - we're always running sites and test environments that way. This needs testing as not seen this before.

  2. This is something to consider for the future when reworking the settings panel

  3. These are your great add ons:
    Adding language translations for add ons needs to be thought about for the future, maybe you can use the built-in front end language selector tool for that for now?

  4. Do you mean what is the best way to make plugins?

  5. Manual to download from the website might be best for now as already want to look at decreasing the size of the ZIP file. Maybe an online wiki or something similar might be best?

  • Plugged in a fix for showing audio/media files in the media folder

This will be in 5.3.3 @annett - thanks for reporting :slight_smile:


1,) If someone opens a page with the "http" link, the page is displayed in unprotected mode.
This applies to free certified sites such as:

1-A,) How to set the .htaccess pulse. for protected mode?
2-A,) Why isn't it good at admin to add the ability to set: "Set Protected Mode"?

4,) This is just a simple question.
How to view Polse code on an exit page?
For example:
This cannot be displayed as a code.

How to properly display it as a code?

I had to try it out with the plugin: "tagcode"

See this page:
Read = "Welcome!"

5,) :disappointed_relieved::sleepy::-1:


This is completely a server task, not an application (Pulse) task.

You or your hosting provider has to take care about the SSL certificate. In oder to redirect from http to https, there are various snippets available in the internet, like:


Well thank you!
I added these two lines to .htaccess.
My hosting provider automatically takes care of and installs (for customer, free) SSL certificate.
I do not agree!

Pulse, when overwriting .htaccess, has to rewrite it correctly.
Not as follows:
RewriteEngine On
RewriteBase /
That's why I am writing about the setup options in admin.


There could be even more options inside an already existing htaccess file, and also some, which are not working with Pulse...


What you've done is pretty cool, font and colour highlight:

You can also maybe use <pre></pre>

Using the redirect as @instacks says should work:

    RewriteCond %{HTTPS} off
    RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI} [R=301,L] 

Adding a "force SSL mode" is a good idea for a future update


As part of a great suggestion from @ezchile here, for moving images in Media to other pagination, we have now added this to the next build (5.3.3) :slight_smile:

  • Re-ordering of images in media can now be dragged and dropped (great for when lots of images exist) with drop targets for next/previous pages

It looks something like this:


...Great! This is going to be really useful.

Suggestions for 5.3.2

Just added to this a couple more good ones:

Almost ready for release this one - not long now :slight_smile:


You're on a roll Michael! Well done...


Thanks @ezchile - we're doing our best :heart_eyes:


More added to the list including this as mentioned in another thread, info on Editor vs User:

Also based on a great idea from @Oliver we've extended the Blog loop to make it more flexible.

Something like:

{{blog-loop-start}} own layout with divs, cards, whatever {{blog-title}} {{blog-content}} etc.

The old parser is still in place so no need to do any updates, but we've added this to see how it goes. We will add more examples of it here once it's finalised before release.


Amazing! Thanks for that, this takes designing the blog to a whole new level.


Oh that sounds great :+1:

If it is possible to wrap that also into RW, I see a lot of potential. Like having a start and end blog tag, and inside other stacks with own styling and text dynamically inserted.