EkoJR

Very odd. I still think something is conflicting with theme. I was looking around to see if I can get the theme so I can duplicate the issue, but it looks like you bought yourself a premium theme. Which makes it pretty hard to figure out on my end. Plus I don’t even know if you can give someone a theme like that to debug on a localhost.

I went through the plugin’s revisions to see what changes I made, and the only related things I see is changes in ‘exclude current’, page and term dynamics, and adding wp_reset_postdata() and wp_reset_query() functions to APLQuery class.

Are you using any ‘include terms’ in your taxonomies, and/or using ‘Current Page’ from your page hierarchy. Then are you using the exclude current function at all?

Lastly, leaves the reset function in the APLQuery.php file. Which I thought would improve the sorting, but could be what’s causing the problem. Plus, after WP’s update, some fixes to WP_Query class cleaned up the issues that I was having during development, which is why I ended up added the reset functions to the current version.

If the first two aren’t the issue, then I would try replacing APLQuery.php by extracting this new file in /wp-content/plugins/advanced-post-list/includes/class/APLQuery.php

the new file is linked on this page under APLQuery File Replace:
APL Version 0.3.b4 Page

I don’t think its related to my plugin, but I do think it is related to a theme that you have active.

The two entries at the bottom both have the same CSS classes from
https://www.slagelsetennis.dk/wp-content/themes/propulsion/propulsion/css/layout.css
AND
https://www.slagelsetennis.dk/wp-content/themes/propulsion/propulsion/css/base.css

Which leads me to believe that it is a theme issue.

Instead of deactivating the other plugins, try deactivating Advanced Post List, but make sure you have the APL admin option settings set to NOT delete the database upon deactivation. Then check the issue to see if it continues, and when you re-activate the APL plugin, your settings should all still be there with 0.3.b4 (others beta versions are bugged).

Huh, I don’t remember marking this as resolved. Did you get your issue fixed?!? or just mark it resolved?

Btw, I still have this issue at the corner of my mind, so you may want to check back every now and then to see if the issue cleared up after a new release version.

Hmm, this is a very odd issue, considering that the post/page attribute shortcodes are only applied when it goes through the call-stack APLCore::APL_display to (private)APLCore::APL_run to APLInternalShortcodeReplace function. So any other post attribute shortcodes shouldn’t be applied before or after the post_list shortcode.

However, if you have a post_list that also displays other posts/pages with post_list shortcode(s), then the (child) post will remain unformatted by the plugin. That is one common issue I see happen to me, and I haven’t yet gotten around to adding support for post list shortcodes within post list shortcodes. So, that’s one issue you may want to check on.

If that isn’t the issue, I got a few questions that currently come to mind.

• Did you have this problem at all in version 0.3.b3? (although you did hint that you did not)
• Have you tried checking if a different plugin is conflicting with the APL plugin? (deactivate them until you find the plugin causing the issue)
• Can you link the URL that is having this issue? (I may be able to inspect it and get a couple of clues as to what the issue is)

Something on your site must be making it hang. I just wish I had a way to debug it myself so I can see exactly whats going on and why. Then correct the issue.

I would recommend using 0.2.0, since it’s the last version without the Custom Taxonomy support. Kalin’s post list had some bugs when it would query posts, and the “Require Categories/Tags’ was one of them. So if your using the require setting, you may want to switch back.

If you were still unable to get the current (0.3.beta3) version working, and would still like to try it out, then I just released a new version 0.3.b4. Hard to tell what the exact problem was, someone else had already reported a similar issue, which could be the same. So I tried to clean things up and optimize it as much as possible. Hope it works out for ya this time.

Sorry about the hold up. I had to take a break and give my brain a rest. After getting some things done to try and fix your issue, I still had more work to do on it before I felt comfortable releasing it. After enjoying some of the nice weather, things have been coming together a lot smoother, and I just released a new version that has multiple bug fixes. I still kind of doubt it will fix your issue, but I tried to lighten the load as much as I can.

If you can, could you let me know things turn out on 0.3.b4. Thanks in advance.

I do plan on adding this, possibly very soon. Originally, the plugin used post_query() to retrieve posts, but with the plugin taking advantage of the WP_Query class. It has opened it up to a multitude of filter setting. Which includes filter settings for authors, but I decided to hold off on adding some additional filters so I can primarily focus on getting the plugin fully functional with Custom Post Types and Taxonomies feature in WordPress.