Forums › Product XML Feeds for WooCommerce › HTTP error 500 – PHP limit
- Support forum for the WooCommerce Product XML Feeds Manager.
- This topic has 10 replies, 2 voices, and was last updated 5 years, 7 months ago by
Terry.
-
AuthorPosts
-
July 17, 2019 at 9:19 pm #105630
Terry
GuestI am getting an HTTP Error 500 when attempting to create a feed with default options… Does this plugin have any minimum requirements in PHP etc.?
-
This topic was modified 1 year, 8 months ago by
Omar Dabbas.
July 19, 2019 at 8:00 pm #105631Terry
GuestSeems woocommerce needed to be updated for it to work? Is there any way to get category tree for a product alg_product_categories seems to return just one category, not the whole structure?
If this can happen then we will gladly buy this plugin so that we can get out of stock filtering and custom update periods. 🙂
July 19, 2019 at 11:32 pm #105632Hi Terry,
Sorry for a late reply.
1. Generally we do try to maintain backward compatibility with older WooCommerce versions. Which WooCommerce version did you have before updating?
2. Actually
[alg_product_categories]
should return all the categories separated by comma. Are you sure your product(s) have multiple categories set? If that’s not the case – could you please try using more general[alg_product_terms]
shortcode, i.e.:[alg_product_terms taxonomy="product_cat"]
July 20, 2019 at 9:34 am #105633Terry
GuestHi, thanks for taking the time to reply.
Was using WooCommerce 2.6.14, and yes you were right, some products had not been created with all the necessary categories selected.
However, now there is another issue. The parent category appears last, e.g. sub_category_1 > sub_category_2 > parent_category, when it should come first. Is there any way to order them?
July 20, 2019 at 5:21 pm #105634Hi Terry,
You are correct – categories should be outputted in alphabetical order (i.e. not hierarchical). Not sure if this will be good enough, but we’ve just released new plugin version 1.5.3, where I’ve added
orderby
attribute to the[alg_product_terms]
shortcode. You can now sort it byparent_id
, i.e.:[alg_product_terms taxonomy="product_cat" orderby="parent_id"]
If you were creating your categories in ascending order, this should give you the required results. Please take a look and let me know what you think.
July 20, 2019 at 10:07 pm #105635Terry
GuestHi, you have been of very helpful and I appreciate it.
However the fix you suggested is not working for us. Categories are displayed in the same way as before despite using the orderby option.
July 21, 2019 at 1:46 pm #105636Hi Terry,
Hmm… That’s a bit weird. Unless your parent IDs match alphabetical order (which is unlikely) you should see different results in resulting XML. Are you sure you’ve updated the plugin to v1.5.3 (if you are using Pro version, you need to update Pro, not free)?
July 21, 2019 at 7:50 pm #105637Terry
GuestHi,
yes, the plugin is updated to the latest version. I am confused as well.I experimented by creating a completely new category hierarchy of six entries and a test product and it works correctly there. But all the existing products experience problems.
Could this be a database issue? Or a plugin conflict?
July 21, 2019 at 9:25 pm #105638Terry
GuestI may have found a very inelegant solution, but if it works I am going to use. Just one question though, is there a limit to the number of value pairs for find/replace in case of multiple items?
July 22, 2019 at 5:13 pm #105639Hi Terry,
No, there is no limit on find/replace pairs, however, I think I’ve managed to implement the hierarchical sorting. Please update the plugin to v1.5.4 and try this:
[alg_product_terms taxonomy="product_cat" orderby="hierarchy"]
Let me know if something is not working as expected.
P.S. If you like the plugin, please consider leaving me a rating.
July 23, 2019 at 7:39 am #105640Terry
GuestAfter the last update and using the hierarchy ordering categories display properly on our staging environment.
However, we had to revert woocommerce version on the live site and we are back too error 500. when trying to create the feed. We will figure it out eventually.
One last request, could you give an example of using multiple find/replace, is there any non allowed characters in-between the separators, etc. I have a suspicion I was doing it wrong. The reason I am asking is that before you updated to 1.5.4 and solved my issue, I was trying to recreate the category hierarchy using the category_url shortcode and replacing strings there with actual category names, but sometimes even if the number of pairs was correct, the find/replace mechanism skipped items, i.e. the first element of the, say 15th pair, would match to the second element of the 17th pair.
-
This topic was modified 1 year, 8 months ago by
-
AuthorPosts
- You must be logged in to reply to this topic.