[Resolved] Problem with fragment identifiers in URLs
I’m a developer at http://www.ecwid.com. We develop a shopping cart solution Ecwid which is used by more than 300.000 people worldwide. We have a plugin for WordPress: http://wordpress.org/plugins/ecwid-shopping-cart/
Some of our clients use your plugin “Shareaholic”. But it’s been discovered that there’s a conflict between Ecwid and Shareaholic, and it impacts the use of Ecwid. More details below. I hope you will help us in solving this problem.
Ecwid, as well as many other applications, uses fragment identifier (http://en.wikipedia.org/wiki/Fragment_identifier) mechanism to address pages. But it’s turned out that Shareaholic forces links formats to be changed from http://example.com#test (that is supposed to address pages of the site according to the above-mentioned mechanism) to this one: http://example.com/test. As a result our plugin isn’t able to address pages properly and doesn’t work.
Most likely this breaks the work of other plugins that use the same approach (standard of fragment identifier).
Is it really required to use that behaviour in your plugin? We believe it’s not quite correct as long as it adversely affects other applications. Unfortunately due to this problem we have to recommend disabling Shareaholic plugin to our clients in order that they could use their shopping carts and continue selling.
We rely you will look into the problem asap and find a solution. Let me know if you need more details.
- The topic ‘[Resolved] Problem with fragment identifiers in URLs’ is closed to new replies.