Erunafailaro

It works with 3.5+ … IT could also be caused by one of your plugins.

Could you please post a screenshot of your blogroll, where we can see in which way it is sorted inproperly?

This is a screenshot from your blogroll.

Looks fine to me. Which way would you like it to be sorted? Maybe it’s an issue with your browser.

hmmm … now I see the problem. Indeed, there is a bug concerning the drag-and-drop. It does not work. Happens also on my blog.

I’ll keep you informed and will release a bugfix within the next days.

I think you are really mixing something up.

Order of the categories has nothing to do with sorting. There is only one way to determine the order of the categories. That is by drag-and-drop. By dragging and dropping you determined the category “*My Blogs” to be the first of the four categories.

That works perfectly as I can see on your screenshot, where you also show your blogroll. The category “*My Blogs” is the first one, followed by “Blogroll”, “Pure Poker” and “Side Trips”.

Reading your first posting of this thread, I understand that the order of the categories is exactly as you want it (correct me, if I am wrong).

Sort order (e.g. alphabetical) determines the order of the bookmarks within each category and not the order of the categories . As you chose to activate Javascript-sorting, alphabetical sorting is overridden by the date-based order of the bookmarks.

If you want the sort order of your bookmarks to be alphabetical within each category, disable Javascript-sorting.

Don’t know how this could happen.

Which version of the plugin are you using? Which of the two different types of the plugin’s widgets are activated in your sidebar? How many of them are active?

Could you post the URL of your blog and a complete screenshot of all your settings for the plugin?

@realtyrealized – confirmed!

Switching to manual does not work if you also add urls of the files that should be minified.

Please visit my wiki: https://wiki.weinschenker.name/feedreadingblogroll:configuration

Right under the headline called Display Options, you will find some info concerning the max number of bookmarks per category.

When you log in to your blog and go to the plugin’s admin page, you will find the option directly under the radio-buttons that are responsible for the blogroll-style.

This screenshot:

https://hydra1ysk.com/images/plugin_problem/configuration1.png

shows that you are not using a valid google API key. Instead, you just made one up yourself. That’s a nice try, but it does not work.

Get a valid API-key and try again.

Here is the link to Google: https://code.google.com/apis/ajaxfeeds/signup.html

It looks like you did not add the widget(s) to your sidebar at all.

Please have a look at this page from the Codex: https://codex.www.ads-software.com/Appearance_Widgets_SubPanel

Go there and move one of the WP Social Blogroll widgets to you sidebar.

Please post the URL of your blog. The URL you supplied above points to the plugin-page.

Hello fernandoagudo,

currently, pagination is beyond the scope of the plugin. I designed it to be a blogroll-widget for the sidebar.

I agree that pagination is a requirement that naturally comes up as soon as you list links on a page. Maybe this plugin is a better one for you: https://www.ads-software.com/extend/plugins/wp-render-blogroll-links

I just made this screenshot from your blog:

https://www.weinschenker.name/downloads/reubenscube.png

I can see your blogroll with your bookmarks including their latest post-title and age of post.

I am afraid your description of the error is a little bit vague for me. What exactly is missing? Please post a screenshot of all your settings from the plugin’s admin-page, so I can see what you have done so far.

Hello,

on the plugin-docu-pages I added a link to my wiki: https://wiki.weinschenker.name/feedreadingblogroll:start

Everything you need is described in the configuration-section.

You may also take a look at my wiki: https://wiki.weinschenker.name/feedreadingblogroll:start

There you will find further documentation.

I can’t promise this feature for the near future. But it is one of the longtime-goals. Unfortunately, it requires an almost complete rewrite of the plugin.

This will take a while. Maybe it is a feature for version 2.0 of the plugin.