search

KeanuTang / query-loop-shortcode

WordPress Plugin for Gutenberg Shortcode Block to Work Within Query Loops
GNU General Public License v3.0
4 stars 0 forks source link

Database values still fetched from first post only #2

Open Knocks opened 1 year ago

Knocks commented 1 year ago

I installed this plugin hoping to resolve the issue of the Gutenberg loop fetching database values from the first post of the loop and showing the same values for all posts. But so far I'm getting the same results as with the standard Gutenberg loop.

Is this plugin intended to address a different issue from the one I'm facing?

KeanuTang commented 1 year ago

It should be fetching the queried posts. What shortcode/plugin are you trying to use? I just checked where I set this up, and it's working correctly.

Knocks commented 12 months ago

I needed to get it to work with plugins that allow voting on posts, such as like/dislike counters. I have tried several of these plugins, and they don't work in loops (only the first post's data is displayed correctly and duplicated in all other posts in the loop). My solution was to install a plugin called Meta Field Block to show like/dislike data directly from post meta in the database.

KeanuTang commented 12 months ago

Ok, I'll try to troubleshoot this further. Looks like you were using posts (my test example uses pages), so I wonder if that's where the problem is coming from.

etzel42 commented 9 months ago

Any updates on this? I am using this plugin with posts too.. @KeanuTang I replied to a wordpress support forum post which you posted a link to your plugin, but for whatever reason it seems to have been removed.. but I had first used the standard shortcode block and had a function to re-render/run do_shortcode() for html, paragraaphs etc and that was working fine. But since WP v6.4 that work around is not working anymore. I found your plugin and thought I'd give it a try, but again that's not working either.

Perhaps its what you're thinking because its on a post and not pages, though I can't imagine it would be much different in the back end.

I just don't get why WP hasn't fixed this issue themselves.. seems like that closed their ticket on the subject and think its fine because someone found the workaround.

Hoping you can update the plugin with a fix!