p14nd4
Forum Replies Created
-
Forum: Plugins
In reply to: [Multi-page Toolkit] Solved: Patch for js errors / "Insert Title" buttonI apparently missed the edit window, but wanted to add that I did go back to grab the original error messages, which may help other people find this in the future:
Uncaught TypeError: Cannot read property 'mce_inline' of undefined tinyMCEPopup.getWindowArg @ tiny_mce_popup.js:47and
Uncaught TypeError: Cannot read property 'plugin_url' of undefined tinyMCEPopup.getWindowArg @ tiny_mce_popup.js:47I’ve also posted this on my blog, and may respond more quickly there if you have comments or questions.
Forum: Plugins
In reply to: [Flickr Photostream] Plugin not working: HTTP/1.1 403 Forbidden errorhow do you install curl?
That will depend on your hosting platform. I, for instance, run a debian web server, so accomplished this by running
sudo aptitude install php5-curl.Other platforms will vary. If you’re on shared hosting, you might be at the mercy of asking the host if they’ll install it for you. Sorry I can’t provide more assistance (at least without more information).
Forum: Plugins
In reply to: [Flickr Photostream] Plugin not working: HTTP/1.1 403 Forbidden errorI just tripped over this, too (and worked around the issue by installing php5-curl).
For those who are interested, I believe the underlying issue is that, as other threads have pointed out, the unencrypted (i.e. http, not https) API is being shut down. The code leading to this error appears to perform manual socket open/write/read stuff in the absence of curl functions, but it’s hard-coded to open a socket on port 80 (http). Unfortunately the solution isn’t as easy as just changing to port 443, since now the communications all need to be encrypted, so simple fputs/fgets calls won’t cut it.
The answer might be that curl is now *required* for this plugin, and the plugin settings page should loudly indicate an error if it’s not present.
A secondary action item would be to adjust this so it doesn’t prevent the rest of the content in a post from being displayed just on account of failure here. Perhaps a suitable $response can be returned instead of just die(), and that’d allow things to carry on?