Hi @Enwikuna
I am so sorry for the inconvenience.
If you are mentioned about this sorting order issue: https://d.pr/v/tBKuYx
Previously, we had some clients facing this exact issue. They all had CloudFlare and server caching issues. After they clear that cache, the issue is fixed.
If you are also using any caching plugin, can you please clear your cache and then temporarily deactivate the caching plugin? After that, to clear the page cache, press cmd/ctrl + Shift + R all together and check.
Let me know how it goes.
Thank You
Hi,
thanks for answering this topic. Since we are also a development company, we’ve cleared all these possibilities before asking a question here. Cleaning the cache don’t solved the problem. Also, we’re not using any service like CloudFlare.
But one question: will the sorting affect the order of the pages within the frontend documentation? The sorting position at the admin dashboard got saved, but I expect the same order inside the docs on the frontend page which are not fitting the order on the admin dashboard. Thats the issue I’m talking about.
Regards
-
This reply was modified 5 months, 1 week ago by
Enwikuna.
-
This reply was modified 5 months, 1 week ago by Enwikuna.
Hi Enwikuna,
It may happen due to the conflict also. Can you please check for plugin conflicts by following this:
Plugin conflict check: Often, we see problems occur in combination with another plugin or theme. The fastest way to rule out any conflict is to temporarily deactivate all the plugins except BetterDocs. Simply go to your WordPress Dashboard and navigate to wp-admin => Plugins, and then deactivate other plugins.
After deactivating all plugins, check if the issue still persists. If the issue goes away, then a plugin conflict is likely.
Enable plugins one by one: Reactivate your plugins one by one, checking the website after each activation to see if the issue reappears. This will help you identify the plugins causing the conflict.
Besides, you can switch to a different theme like Astra, Flexia, or Twenty Twenty Three. And, check back as well.
Let us know how it goes.
Thank you!
Hi,
thanks for getting back on us. We’ve already checked everything. Also, we have checked your source code. It looks like that the sorting order is not getting applied to the frontend order. I think you need to improve the code here. If you’re not able too, we will do it and let you know how we’ve fixed it.
Regards
Johannes
Hi,
little update. We’ve checked the code again. Since we are using nested categories, when we order documents inside a nested category, the _docs_order term meta is getting saved to the nested category, which makes sense.
Now, inside your Query.php file, you are hooking into the pre_get_posts hook to read the custom order. The only issue is, that you are now looking for the order on the main / parent / top category, which don’t have any of our custom orders as meta.
This results in a non-ordered category. On the admin dashboard, you are using the correct sub-category ID to read the order. Because of this fact, it’s correct on the admin dashboard but not on the frontend.
I would say, this is a little bug you need to fix asap since it ruins our whole user experience. We will try to fix it for you, but we have a very limited time and knowledge about your code. It will cost us a lot of time.
Regards
-
This reply was modified 5 months ago by Enwikuna.
Hi,
another update which (we think) fixes the issue with the ordered sub-categories. Not sure, if this is the ideal way to go, but for now, it will fix the issue for us until you publish a bugfix update.
After finding out that the sub-categories are affected, we’ve checked your code again and found the following function inside the Query.php:
public function docs_query_args( $args, $filter = [] )
This function get’s called from the nested-categories.php template part. Below the following code, we’ve added some custom code to get the ordering to work. The ordering is now correct – related to the admin order:
$tax_query = [
[
'taxonomy' => 'doc_category',
'field' => 'slug',
'terms' => $_term_slug,
'operator' => 'AND',
'include_children' => false,
]
];
$args['orderby'] = 'post__in';
$args['post__in'] = $this->get_docs_order_by_terms($_term_id);
The code inside the pre_get_posts hook as described above only covers the main category sorting (in case the sorting is done inside a main category, not a sub-category).
We hope, that it helps you to fix the bug (the correct way). Also, we would be very happy if it would be something worth for you. Maybe a 1-year pro subscription? We would love to try out some pro features 🙂
-
This reply was modified 5 months ago by Enwikuna.
Hi Enwikuna,
Thank you so much for sharing the details with us. I’m delighted to hear that your issue has been resolved. I will inform the team regarding this. Also, we will inform you if we get any update from the team regarding your request.
Please feel free to let us know if you need any assistance further or have any queries.
Thank you.
Have a good day! 😊
Hello,
many versions later, this bug is still present! Please fix it asap!!!
Hi Enwikuna,
We are really sorry to hear that. Will you please tell me if you are getting this sorting order issue with the BetterDocs latest version also? Please update the plugin to the latest version 3.5.5 and check if that resolves your order issue.
Let us know the update.
Thank you.
Hi,
the sorting inside the admin dashboard is still not applying to the frontend. The caching is disabled. When checking the source code, I can not see any of my suggested improvements to fix this issue. We have reverted to our backup containing the fix we’ve done. We will wait for you to get in touch with the devs to tell them about this issue and ask them to fix it. Since we have a lot of docs, sorting them is a feature that needs to work!
We have indeed checked it with the newest version!
Regards
Hi Enwikuna
I sincerely apologize for the ongoing issue with the sorting functionality in the admin dashboard. I understand the importance of this feature for managing your documents.
Please be assured that we haven’t overlooked your suggestions. We immediately shared the information and code you provided with our development team. Currently, the fix is undergoing thorough testing to ensure everything works as intended.
I’ll keep you updated on the progress and let you know as soon as the fix is ready to be deployed. In the meantime, if you have any further questions or concerns, please don’t hesitate to reach out.
Thank you for your patience and understanding.
Hi,
it’s still not fixed! This is a urgent bug and you’re not even trying to fix it. We will search for a different solution we can rely on.
Regards
Hi Enwikuna,
We regret the inconvenience caused by this issue. We are assuring you that our development team is currently conducting a thorough investigation, and the process is underway. Once the issue has been addressed, we’ll proceed with testing the fixed version to ensure everything functions as expected.
I’ll keep you informed about the progress and notify you as soon as the fix is ready for deployment. If you have any additional questions or concerns in the meantime, please feel free to reach out.
Thank you for your patience and understanding.
Hi Enwikuna,
I hope you are doing well.
I’m pleased to share the good news that this issue has been successfully addressed. To ensure you benefit from this fix, kindly download the BetterDocs plugin from here: https://d.pr/f/HUNZHj.
Your prompt update will guarantee the resolution of the mentioned issue.
Thank you for your cooperation 😊
Hi Enwikuna,
I hope you are doing well.
We haven’t heard from you since then. Can you please inform me whether the issue mentioned above is already fixed with the Dev version I provided or not?
Let us know the update.
Thank you.
Have a good day!
