![]() But they are ubiquitous, and implementing support for one of these standards opens the doors to dozens if not hundreds of clients on every conceivable platform. These XMLRPC APIs, based on the venerable MetaWeblog, are not great. Obviously it would be a lot less work for me, and I’m generally cautious about taking on the burden of developing support for yet another all-new, custom API with all of its own nuanced behaviors.īut option #1 would also be better for Squarespace, in that support would be instantly restored to MarsEdit and any other 3rd party clients using the Squarespace 5 API. Implement an entirely new API, unique to Squarespace, that I could consider implementing support for.Somehow get support for one of the standard APIs working with their new engine.The two possible solutions that leap to my mind are: I have been holding out hope that Squarespace will eventually address the shortcoming. Of course, as a developer with customers who depend on this support, I was disappointed to learn this. I had some cordial correspondence with staff at Squarespace, who explained that because of the laudable flexibility of the new version, it’s difficult to provide access to the content with one of the standard blogging APIs that MarsEdit uses to connect to Squarespace 5 and dozens of other services. It came as a surprise when Squarespace 6 was released earlier this year, that support for 3rd party editors such as MarsEdit was dropped from the service. MarsEdit has supported Squarespace for years, and a number of our mutual customers have come to rely upon the app as a convenient means of managing content for Squarespace sites from the Mac desktop.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |