4 ms·
Really cool, I’ve toyed with this idea before. Unfortunately the challenge is interactive plugins. I’m skeptical of your solution to effectively build a white
by chatmasta 9y ago
Really cool, I’ve toyed with this idea before.
Unfortunately the challenge is interactive plugins. I’m skeptical of your solution to effectively build a white list of supported plugins. This will obviously be a dealbreaker for many sites.
Off the top of my head, here’s how I would solve it:
- The user hosts their “origin” WP site on a separate subdomain from the main site and leaves it running
- Your product scrapes from that subdomain. When it encounters any page with a form action, it rewrites the form action to point to the origin subdomain
- If it detects dynamic content on the page (not sure on best way to do this), or the request follows a form action, it registers a CACHE_MISS for the page and fetches it from the origin subdomain
- zener79 9y agoYep, you get the point. Plugin support is a real challenge... anyway we are seriously building a white list of compatible plugins, and so far they are about 90% of the total. For the remaining 10% it is usually always possible to replace them with some external service (facebook-comments or disqus for comments, our Zapier app for mailchimp/drive/dropbox integration, beds24 as booking system, etc) We also thought about something like your idea (keep a second installation live somewhere to submit the data), but, as you will have to host your real WP somewhere, you will lose one of the main benefits of HardyPress, namely to have your site unbreakable.
- chatmasta 9y agoWhat about custom plugins (developed in house by your customer)? For your point about security, that could be solved by asking them to whitelist your resolver IPs at the origin. Or you could even host the “origin” for them, in a closed network.