Xedin Unknown

Hi Mrgrain,

This is not what happens. The code is trying to include a class with the fully qualified class name “Logger” which happens to be an un-namespaced.

This is exactly what happens. The fully qualified name of the logger class is Aventura\Wprss\Core\Component\Logger. Like I explained in my previous post, this is inferred, with the ability to look up a class in the root namespace, which is the case here due to that class existing, when it should not, in fact, exist.

Looking forward to news with regard to Instant Articles for WP.

Hi Mrgrain,

And thank you for this very comprehensive bug report.

The ComponentFactory::createComponent() method is there to precisely ensure that all components are in fact components – this is achieved by throwing an exception – and to allow requesting components by a short name, which by default resolves to a class identified by the name, or, if it doesn’t exist, to the same class in the same namespace as the rest of the components – which is the most common scenario, and intended behaviour. It is not possible to alter this behaviour just for the logger only.
On the other hand, it is clearly a bug on the part of “Instant Articles for WP”: one should never declare un-namespaced classes because they may be declared by someone else. Indeed, if we had done the same by declaring the Logger class in the root namesapace, which is unfortunately common practice, consequences would be dire, which is why our class is contained in a namespace, according to the specification of PSR-4.

We will take this incompatibility into account in future releases, and will consider implementing your suggestion. Meanwhile, I recommend that you contact the author of “Instant Articles for WP” and tell them of this incompatibility. We would also love to hear back from you with results of your interaction with the developers of the “Instant Articles for WP” plugin, and are open to suggestions and collaboration.

We appreciate your feedback, and thank you for choosing WP RSS Aggregator.

Hi blkedy!

Looks like you’ve found the solution. Would you mind letting us know whether it worked?

Hi wordpress2075,

Sorry to hear that you are having trouble using our plugin.
Could you kindly explain in more detail the symptoms you are experiencing? Please include examples and screenshots, where applicable, and if possible – steps to reproduce.

Hi all!

Apologies for not posting any updates for a long time. Unfortunately, we are still unable to reproduce the issue on our end. If one of you is experiencing the symptoms consistently, and is willing and able to help come up with a definitive set of steps to reproduce this, please contact us through our premium support channel.

Thanks!

Hi popidev!

Could you kindly explain what kind of restrictions you have in place, including configuration and code where applicable? If you include that in your reply, we can look into why this may influence import, and how this can be changed.

Hi 00coday!

Sorry to hear that you may be having trouble with our products.
As far as I can see, WP RSS Aggregator does not interfere with wp_insert_post. We do hook into the postmeta creation and updating procedures, as well as post updating, but all strictly for feed sources.

Could you kindly describe the symptoms, and explain why you think there may be a link between them and WP RSS Aggregator?

Hi divithemeexamples,

Judging by the markup, doesn’t look like the sidebar is added by WP RSS Aggregator. I assume you are displaying the imported items using the shortcode. Does the sidebar remain if you remove the shortcode?

Also, it looks like you are using the Excerpts & Thumbnails add-on. If so, and the problem persists, please contact us via the premium support channel.

Hi altruetech,

Sorry to see that you have issues using the plugin.

While we have documented this problem and will be likely including a fix in the next release, please try going to the RSS Aggreagator > Settings page, and clicking “Save Settings”.
If this doesn’t help, it should be safe to ignore these messages until the fix is out. They will also not be visible if you have WP_DEBUG or WP_DEBUG_DISPLAY off.

Hi,

The error you received indicates that at that particular moment in time the Feed to Post add-on was active, but the core WP RSS Aggregator plugin was not. The core plugin must always be active when add-ons are active. Under normal circumstances, it should be impossible for an administrator to activate one of our add-ons without having the core plugin active; however, it is possible that this happens as a result of some error internal to WordPress, such as if the core plugin fails to update for some reason. So, to answer your question, it should not be necessary to de-activate add-ons to update the core plugin; however, in your case it may be necessary, if you continue receiving such errors.

We will look further into this, and if we find a problem that we can fix, the fix will be included into one of the future releases. Thank you for reporting this. If you continue having this problem, or other problems related to add-ons, please get in touch with us via the Premium support service.

Hi,

Sorry to hear you are having problems.

One reason for error 500 is that your web server may be misconfigured. If you are sure that your web server is configured properly, this error can be caused by PHP encountering a fatal error, but not being able to display that error due to error reporting settings. If you wish to display the error text, please make sure that both WP_DEBUG and WP_DEBUG_DISPLAY are set to true.

Hi,

Sorry for this delay. There were a few more changes that fixed bugs and made urgent improvements to the plugin. However, the wait is almost over, and you should be able to update tomorrow.

Thank you for your patience.

Hi sojournerweb,

There are a number of key steps to take in order for you to achieve what you want.

1. Understand what you are sorting by;
2. Determine how you are displaying the feed items;
3. Understand the parameters.

1. This is the most straight-forward one. If you are sorting by post_date, you can skip this. Otherwise, see point 3.
2. This is most important. Logically, it is not possible to sort items differently for feed sources in the same query. However, it’s possible to change sort order depending on the feed source ID. What you could do is detect the presence of a specific source ID, and change the sort order accordingly. Thus, if that ID is present in the list of IDs you supply via the shortcode, the items will be sorted one way, if not – then another way.
3. Most technical part.
If you are sorting by something other than post_date, see this page.
The IDs of the feed sources that are passed to the shortcode are in an array that is stored in $args['meta_query']['wprss_feed_id']. It’s a numeric array, so you would probably have to use in_array().

I hope this helps. Please give it a go and let us know if it doesn’t work!

According to our tests, this issue does not present on PHP 5.3.14 or 5.3.28. All concerned parties are advised to switch to one of these versions as a temporary measure.

Dear all,

Could those of you who are getting the “Can’t inherit abstract function” error kindly post the version of PHP you are running? You can quickly find that out from the “System Information” section of the “RSS Aggregator” > “Debugging” page in the backend. This would really help us pinpoint the origin of the issue faster.

Thanks in advance!