[Plugin: Advanced XML Reader] Loop through multiple XML files

I understand your problem, but it’s a very specific problem and I think the plugin is not the right place to fix this individual problem. But, it is possible to tweak the plugin and create a custom plugin.

I hope I informed you enough.
Kind regards,
RaymondDesign

Thanks for your prompt response. I was afraid that would be the answer. Thanks so much, I’ll see what I can do.

It’s not difficult when you have some knowledge about PHP.

When you have any problems, you can always contact me:
– using these forums
– on dev.raymonddesign.nl
– on https://www.raymonddesign.nl/contact.html (it’s in dutch, but I think you’ll understand it, it’s just a contact form)

RaymondDesign

Thanks, while I can navigate through PHP enough to understand what the code is doing, beyond making extremely simplistic changes, I don’t work in PHP.
So while not difficult for someone with knowledge of PHP, currently beyond my scope of knowledge.

Hi,
I have exactly the same problem. I am almost sure many more people with affiliated suppliers would like to have this feature plus a more comprehensive parser. I would even pay for it -:)

I’ll see what I can do for you. Maybe it’s possible to add this to the new version I’m currently working on.

Did you ever work on this?
It seems like you could use a parameter to the shortcode to indicate the xml file, instead of storing it in the options. Or have that xml file be the default if none is specified.

Hi Joy,
That’s exactly what I was thinking. Unfortunately I don’t have much time at this moment. My plan is to fully rewrite the plugin. But I have more important things to do at this moment, as I work on this plugin in my spare time. Here’s a poll with to two options of the new version: https://dev.raymonddesign.nl/2012/01/need-your-help/
As you can see, many people prefer the one with a config page. I’m still in doubt about the best solution.

I haven’t actually looked at the code for this plugin.
I think if you modularize the code, you could easily solve more problems.
The code to extract a tag should be one piece. It shouldn’t matter to it which file the xml came from. It should just extract the tag (and apply_filters or do_action when it finds it) and return it.
The code to read the xml file is also independent. It should be given a filename and return the xml.
Then the code that handles the options is separate. The shortcode can be invoked with or without a filename. The shortcode handler would check for the filename and if it didn’t have one, look in the options.

With it all separate, user code could be invoked on the hooks to store the data or total it or email it or whatever. This way, you aren’t limited to one xml file or one tag from the file.

Thanks Joy!
That sounds very nice. The code is sort of modular right now (there are some functions), but it is not real Object Oriented. But, you gave me a very nice start. When I have some time I’ll bring this to a real version.