roundaboutweb

??

Thank you very much, that was helpful.
So the extension “_Veranstalter” was missing. Now it works.

One more quick question:
Where is there an overview of the available icons (e.g. “em-icon-category”, “em-icon-clock”, …)

Thanks, this was helpful. But how can I hide the display if the attribute has no content? I seem to be using the wrong syntax:

            {has_att}
            <div class="em-item-meta-line em-item-taxonomy em-event-att">
                <span class="em-icon-category em-icon"></span>              
                <div>Veranstalter: #_ATT{Veranstalter}</div>
            </div>
            {/has_att}

Presumably “_att” and “em-event-att” is wrong, but what should be there instead?

I found it on my self.

Veranstaltunge –> Einstellungen –> Formatierung –> Default Veranstaltung Raster format

<div class="em-item-meta-line em-item-taxonomy em-event-categories">
	<span class="em-icon-category em-icon"></span>
	<div>#_EVENTCATEGORIES</div>
</div>

The real question is why WooCommerce is still using an outdated version of the JavaScript library, or when an update can be expected.

Perfect, thank you very much.
Is it possible to create your own templates in the Pro version, which are then update-proof?

Thanks for the info, but is it possible that you can only assign a design for a slider but not for a carousel?

[recent_post_carousel design="design-1" media_size="thumbnail" speed="7000" category="31" slides_to_show="4" content_words_limit="10"]

design-1.php:

<h4 class="wppsac-post-title">
     <a href="<?php the_permalink(); ?>"><?php the_title(); ?></a>
 </h4>
...
<?php if( $showreadmore ) { ?>
    <a class="wppsac-readmorebtn" href="<?php the_permalink(); ?>"><?php
esc_html_e( 'Weiterlesen', 'wp-responsive-recent-post-slider' ); ?></a>
<?php } ?>

Both changes are not applied (cache has been cleared):

https://nextcloud.roundaboutweb.info/index.php/s/Z6LKMtgf8j6kgx7

Question 1:
How can the heading type (h2) be changed for the carousel, or how can a design be defined for a carousel?
Question 2:
How can the button text “Read More” be changed/translated?

It’s not about the font size but about the definition of the type! The heading type must have a certain order of precedence (H1, H2, H3 …), as with a table of contents.
Therefore I need the possibility to change the type from “H2” to another (H4).

The FTP user has write access to defined directories below “wp-content”. The “wp-content” folder itself does not have write permissions for anyone in normal operation. The rights are only changed temporarily for installations and updates.

wp-content: 555
wp-content/plugins/: 555
wp-content/uploads/: 755

Fine, now it work.

All directories below “uploads” have write permission (755) and the file “/dlm_uploads/.htaccess” has permission 644.
For some reason, your plugin requires write permission directly to the “wp-content” folder and that is a problem!
The folder “wp-content” does not have write permission, only the subdirectory “uploads” and all folders below it.

In my opinion, the error is due to the fact that you are checking the write permission for “wp-content” instead of “uploads”. Please correct your script so that we can continue to use your plugin.

• This reply was modified 6 months, 2 weeks ago by roundaboutweb.

All WP installations that I maintain have the right 555 for wp-content and only in one case there is an error, namely on the only page with the plugin “Download Monitor”. The error only occurs when you click on Downloads –> Create.

https://nextcloud.roundaboutweb.info/index.php/s/Sr7p37LKLQCHmCa

• This reply was modified 6 months, 2 weeks ago by roundaboutweb.

Is there any hope of an answer?

You can reproduce the error yourself by changing the permissions for “wp-content” to 555.
But I would also like to add the error message here:

PHP Fatal error: Uncaught TypeError: ftp_nlist(): Argument #1 ($ftp) must be of type FTP\Connection, null given in /.../wp-admin/includes/class-wp-filesystem-ftpext.php:438
Stack trace: 
0 /.../wp-admin/includes/class-wp-filesystem-ftpext.php(438): ftp_nlist(NULL, '…') 
1 /.../wp-admin/includes/class-wp-filesystem-ftpext.php(456): WP_Filesystem_FTPext->exists('…') 
2 /.../wp-admin/includes/class-wp-filesystem-ftpext.php(757): WP_Filesystem_FTPext->is_file('…')

In my projects, the “wp-content” folder is always write-protected and only defined subdirectories (e.g. “uploads”) are given write permission. However, as soon as I activate this write protection, your plugin causes a “fatal error”.
For security reasons, customers do not want to do without write protection (which makes sense). Since this problem only occurs with the “Download Monitor” plugin, we need a functional solution for the plugin or we will have to look for another solution. I therefore hope that you can offer a solution in a timely manner, as is the case with all other plugins.