Miguel Muscat

Hi @maestrosombrita,

This forum is dedicated to the free version of the plugin only. For questions regarding the premium add-ons, kindly contact us through our site using the form on this page: https://www.wprssaggregator.com/contact/

Thanks!

@tarheelmm You didn’t specify, but I assume you wish to strip the tags from the title, correct? If so, you need to change “post_content” with “post_title” in the filter. Like so:

add_filter( 'wprss_populate_post_data', 'my_strip_tags', 1000, 2 );
function my_strip_tags( $args, $item ) {
    $args['post_title'] = strip_tags( $args['post_title'], '<b>' );
    return $args;
}

• This reply was modified 5 years, 4 months ago by Miguel Muscat.

@iannnnn The custom feed can only be customized by editing the plugin’s code. However, if you update the plugin in the future you will lose those changes. So before an update you will need to backup your customizations and then apply them again after the update.

If you think you can make these customizations yourself, the code can be found in wp-rss-aggregator/templates/custom-feed.

In the future, we may add some feature that could allow you to change the type of the custom feed so that the plugin will add the correct tags without needing customization.

Hi @dobihobbho. This is a very weird warning that you are seeing. This warning seems to be triggered when WordPress behaves abnormally. We haven’t seen anything like this up till now, so we suspect that you might have another plugin that is interfering with WordPress’ meta functions.

We’ll add some code to make sure that the warning is not shown in such cases. Keep an eye out of the next update.

Hi all. We had explicitly removed the ability to import items with future dates. This was because of timezone differences between the feed and your site accidentally making items being imported as “Future”.

Given the demand that you’ve all brought forward, we’ll be adding an option to feed sources that will re-enable this behavior. Does that sound good?

Our plugin does register feed item as a Custom Post Type, but marks it as private. This means that feed items do not get an archive page and are not included in search results.

By default, PolyLang only works with public custom post types. We can extend that using one of PolyLang’s own filters.

We’ll be in contact with the PolyLang team to ensure that the patch works and then work on getting the patch out in one of the coming updates.

Thank you for your patience.

• This reply was modified 5 years, 4 months ago by Miguel Muscat.

Hi @geonickpal

<pubDate> is an RSS 2.0 element. Our plugin uses the Atom format, which is a more modern specification for feeds. Would the Atom <published> element work for you?

@hcarrier Hey, just letting you know that we’ve found what’s causing the security alert. It was indeed a false positive, so we can safely assure you that it’s harmless. We’ll still be working on changing the affected code. The next update of plugin should resolve these security alerts.

@markdigidigi I don’t think the RSS feeds not validating would cause 500 server errors. It’s most likely to do with the log table not being created correctly.

Can you try using the latest versions of the plugin? We’ve added options in the latest version to disable the plugin’s logging, which might solve your problem.

@maximledoux All our plugin’s meta keys are prefixed with wprss_. However, we strongly advise not deleting everything. A better way would be to use a query that specifically targets post meta that is not attached to an existing post. Here’s an example.

DELETE meta
FROM wp_postmeta meta
LEFT JOIN wp_posts post ON post.ID = meta.post_id
WHERE post.ID IS NULL

Do NOT copy and paste this query. We advise asking your host for help with this matter as your table names may be different.

We will be releasing an update of the plugin early this week that should resolve this issue. We apologize for the inconvenience and thank you for your patience.

@davet The issue you are experiencing is caused by a corrupt version of the plugin. You should be able to resolve the issue simply by deleting the plugin and re-
downloading the latest version.

@maximledoux Thank you for sharing.

Those that do not have access to WP CLI can deactivate the plugin and ask their host to help them run a database query that deletes posts with post_type equal to wprss_feed_template, and then delete the orphaned meta data from the postmeta table. The plugin can then be reactivated once a fresh copy of version 4.14 has been downloaded.

You’re welcome ??

@axellle1 I’m glad that solved the problem for you. Was it only that 1 file that caused the problem?

@axellle1 The error message is basically saying that the plugin has missing files that it requires. How are you attempting to installing? Are you uploading a zip file or installing it through WordPress directly? The latter option is usually preferred since it’s a download instead of an upload, which typically reduces the chance of failure.