{"id":1535,"date":"2010-05-30T15:07:26","date_gmt":"2010-05-30T06:07:26","guid":{"rendered":"https:\/\/regex.info\/blog\/lightroom-goodies\/faq"},"modified":"2010-06-02T08:43:05","modified_gmt":"2010-06-01T23:43:05","slug":"faq","status":"publish","type":"page","link":"https:\/\/regex.info\/blog\/lightroom-goodies\/faq","title":{"rendered":"FAQ for Jeffrey&#8217;s Plugins for Adobe Lightroom"},"content":{"rendered":"<style type=\"text\/css\">\n  .post_container {\n      background-color: #181818;\n      background-image: url(http:\/\/regex.info\/i\/s\/me.jpg);\n      background-repeat: no-repeat;\n      background-position: top right;\n   }\n   .x {\n\n      float:right;\n      clear: right;\n      border:none;\n      font-size: 0px;\n      height: 10px;\n      padding: 0px;\n      margin: 0px;\n  }\n<\/style><!--[if IE]><div style='visibility:hidden; margin:0; padding:0; max-height:1px; font-size:1px'> <\/div><![endif]-->\n<div class='x' style='width:430px'><\/div>\n<div class='x' style='width:426px'><\/div>\n<div class='x' style='width:421px'><\/div>\n<div class='x' style='width:417px'><\/div>\n<div class='x' style='width:412px'><\/div>\n<div class='x' style='width:408px'><\/div>\n<div class='x' style='width:403px'><\/div>\n<div class='x' style='width:399px'><\/div>\n<div class='x' style='width:394px'><\/div>\n<div class='x' style='width:390px'><\/div>\n<div class='x' style='width:385px'><\/div>\n<div class='x' style='width:381px'><\/div>\n<div class='x' style='width:376px'><\/div>\n<div class='x' style='width:372px'><\/div>\n<div class='x' style='width:367px'><\/div>\n<div class='x' style='width:363px'><\/div>\n<div class='x' style='width:358px'><\/div>\n<div class='x' style='width:354px'><\/div>\n<div class='x' style='width:349px'><\/div>\n<div class='x' style='width:345px'><\/div>\n<div class='x' style='width:340px'><\/div>\n<div class='x' style='width:336px'><\/div>\n<div class='x' style='width:331px'><\/div>\n<div class='x' style='width:327px'><\/div>\n<div class='x' style='width:322px'><\/div>\n<div class='x' style='width:318px'><\/div>\n<div class='x' style='width:313px; height:30px'><\/div>\n<div class='x' style='width:309px'><\/div>\n<div class='x' style='width:304px'><\/div>\n<div class='x' style='width:300px'><\/div>\n<div class='x' style='width:295px'><\/div>\n<div class='x' style='width:291px'><\/div>\n<div class='x' style='width:286px'><\/div>\n<div class='x' style='width:282px'><\/div>\n<div class='x' style='width:277px'><\/div>\n<div class='x' style='width:273px'><\/div>\n<div class='x' style='width:268px'><\/div>\n<div class='x' style='width:264px'><\/div>\n<div class='x' style='width:259px'><\/div>\n<div class='x' style='width:255px'><\/div>\n<div class='x' style='width:251px'><\/div>\n<div class='x' style='width:247px'><\/div>\n<div class='x' style='width:243px'><\/div>\n\n\n<p>This page covers the answer to common questions that I (<a\nhref='https:\/\/regex.info\/blog\/'>Jeffrey Friedl<\/a>, an American software guy\nand hobby photographer in Kyoto) get about <a\nhref='https:\/\/regex.info\/blog\/lightroom-goodies'>my plugins for Adobe\nLightroom<\/a>. Most days, it seems, I spend more time answering emails than\nI do developing new features or fixing bugs, so this page is an\nattempt to become a bit more efficient all around.<\/p>\n\n<style>\n    li.tocq { margin-bottom: 20px }\n\n    a[href].q1:visited { color: #BBF }\n    a[href].q1:link    { color: #DC9 }\n    li.bodyq  { margin-bottom: 50px }\n    a.q2      { color: yellow; font-size:120% }\n    span.meta { font-size: 80%; color: #555 }\n    a[href]:link.permalink { color: #777 }\n    .QL li {  margin-bottom: 10px }\n<\/style>    \n\n\n\n<p class='h1'>Installing<\/p><ul>\n<li class='tocq'><a class='q1' href='#disabled'>I get &#8220;<i>An error occurred while reading the schema for the plug-in. The plug-in will be disabled.<\/i>&#8221; What's wrong?<\/a><\/li><li class='tocq'><a class='q1' href='#configure'>Every time I start Lightroom, I get a message long the lines of &#8220;<i>Lightroom needs to configure your system for the ..... plug-in.<\/i>&#8221;.<\/a><\/li><li class='tocq'><a class='q1' href='#baddownload'>I can't install the plugin... I get various errors when I try to install it in the Plugin Manager<\/a><\/li><li class='tocq'><a class='q1' href='#disappear'>I had the plugin installed before, but suddenly it's missing... where did it go?<\/a><\/li><li class='tocq'><a class='q1' href='#old-style-install'>The &#8220;remove&#8221; button in the Plugin manager is grayed out, and I get an error when I try to upgrade.<\/a><\/li><li class='tocq'><a class='q1' href='#upgrade'>I get an error when upgrading the plugin via the built-in &#8220;upgrade&#8221; button.<\/a><\/li><\/ul>\n\n\n\n<p class='h1'>General<\/p><ul>\n<li class='tocq'><a class='q1' href='#packed'>I sometimes get &#8220;Assertion failed: packed&#8221; when using your plugins<\/a><\/li><li class='tocq'><a class='q1' href='#mail'>Why didn't you respond to my note about <i>(insert something unrelated to my plugins, tangential, or something already answered on my site)<\/i>?????<\/a><\/li><li class='tocq'><a class='q1' href='#comparison'>What's the difference between your upload-to-<i>xxxxxxx<\/i> plugin and the one of the same name that comes with Lightroom?<\/a><\/li><li class='tocq'><a class='q1' href='#avail'>Do you have a plugin for uploading to <i>(insert name here)<\/i>?<\/a><\/li><li class='tocq'><a class='q1' href='#log'>I'm running into troubles with the plugin... is there a log or something I can send that might help you diagnose the problem?<\/a><\/li><li class='tocq'><a class='q1' href='#mogrify'>About your LR\/Mogrify plugin, could you please...<\/a><\/li><li class='tocq'><a class='q1' href='#lion'>I can't find my downloaded plugins in OSX Lion<\/a><\/li><li class='tocq'><a class='q1' href='#state'>Why does the plugin sometimes fail with &#8220;The handle is in the wrong state for the requested operation&#8221;?<\/a><\/li><li class='tocq'><a class='q1' href='#earth'>In the Geoencoding Support plugin, the &#8220;<i>Geoencode selected photos from Google Earth<\/i>&#8221; feature doesn't work... it results in an &#8220;<i>Can't get location from Google Earth<\/i>&#8221; error.<\/a><\/li><li class='tocq'><a class='q1' href='#republish'>Photos keep showing up in &#8220;Modified Photos to Re-Publish&#8221; even though I didn't change anything.<\/a><\/li><\/ul>\n\n\n\n<p class='h1'>Network<\/p><ul>\n<li class='tocq'><a class='q1' href='#handler'>When trying to authenticate my login, my browser says it doesn't know how to handle &#8220;<b>lightroom:\/\/...<\/b>&#8221; links; what's wrong?<\/a><\/li><li class='tocq'><a class='q1' href='#sec_error'>I keep getting &#8220;Security Error&#8221; when trying to upload.<\/a><\/li><li class='tocq'><a class='q1' href='#networking'>I keep running into networking errors (&#8220;Unexpected reply...&#8221;, &#8220;no reply...&#8221;, &#8220;timeout...&#8221;, etc.)<\/a><\/li><\/ul>\n\n\n\n<p class='h1'>Registration<\/p><ul>\n<li class='tocq'><a class='q1' href='#cc_reg'>With my new Creative-Cloud install, I can't register my plugins because instead of the registration button the Plugin Manager shows \"<i>Plugin registration button appears here after Lightroom is registered with Adobe<\/i>\".<\/a><\/li><li class='tocq'><a class='q1' href='#reg_code'>I generated a transaction at PayPal (see, here's my PayPal receipt as proof)... when will you send me the registration code?<\/a><\/li><li class='tocq'><a class='q1' href='#reg_server_connect'>When I try to register from within the plugin, I get a &#8220;<i>Can't contact Jeffrey's server<\/i>&#8221; error.<\/a><\/li><li class='tocq'><a class='q1' href='#rc'>The plugin says &#8220;<i>Plugin registration button appears after Lightroom is registered with Adobe.<\/i>&#8221;, but Lightroom doesn't give me a place to enter my Lightroom  serial number.<\/a><\/li><li class='tocq'><a class='q1' href='#upgrade_registration'>My plugin registration code doesn't work after upgrading Lightroom to the latest major release.<\/a><\/li><li class='tocq'><a class='q1' href='#bad-preferences'>I registered the plugin before, but now it's not registered... what happened?<\/a><\/li><\/ul>\n\n\n\n<p class='h1'>Uploading<\/p><ul>\n<li class='tocq'><a class='q1' href='#cookies'>I get a &#8220;missing destination cookies&#8221; error when trying to publish.<\/a><\/li><li class='tocq'><a class='q1' href='#corrupt-settings'>I get a &#8220;corrupt collection settings&#8221; error when trying to publish.<\/a><\/li><li class='tocq'><a class='q1' href='#new-smugmug'>The SmugMug plugin won't let me set the image <i>Caption<\/i> and other &#8220;New SmugMug&#8221; things<\/a><\/li><li class='tocq'><a class='q1' href='#original'>I don't see Lightroom editing changes in the copies uploaded to <i>online photo-hosting service<\/i>...<\/a><\/li><\/ul>\n<hr style='margin: 100px 0'\/>\n\n\n\n<p class='h1'>Installing<\/p><ul>\n\n<li class='bodyq' id='disabled'>\n   <a class='q2' >I get &#8220;<i>An error occurred while reading the schema for the plug-in. The plug-in will be disabled.<\/i>&#8221; What's wrong?<\/a>\n   <br\/>\n   <span class='meta'>\n     <a class='permalink' href='#disabled'>permalink<\/a>\n     &middot;\n     Last Updated: Tue Jun 18 22:51:52 2013 UTC\n   <\/span>\n\n   <p>That's the general &#8220;something went wrong&#8221; message that\nLightroom gives when it has trouble loading a plugin; that message does not\ncontain information about <i>what<\/i> went wrong, so you have to look\nfurther for the cause.<\/p>\n\n<p><b>If you'd just upgraded a plugin<\/b>, please first try restarting Lightroom. Lightroom won't recognize new files in an upgraded plugin until Lightroom is restarted; I try to limit the need for this, but sometimes it's unavoidable, sorry.<\/p>\n\n<p>Otherwise, check the upper-right and lower-right sections of the plugin manager for\ndiagnostics.<\/p>\n\n<p>In the lower-right section, you have to save the diagnostics to a text\nfile, then inspect the text file to see the error messages... <b>only the\nfirst message matters<\/b>. (Anything after that is a ripple effect that\ndoesn't help point to the root cause.)<\/p>\n\n<p>If the diagnostics are not helpful, it could just be that your plugin\ninstall became corrupt (a file in the plugin got deleted somehow, or maybe\nthe entire plugin was moved or deleted?), so perhaps it's easiest to simply\ndelete all copies of the plugin from disk, replacing with the latest\nversion from my site, perhaps re-adding the plugin via the plugin manager\nif the location on disk you choose for the latest download is not where it\nwas before. In any case, all plugin data remains intact; you never loose\nany data by deleting the plugin and reinstalling.<\/p>\n\n<\/li>\n\n<li class='bodyq' id='configure'>\n   <a class='q2' >Every time I start Lightroom, I get a message long the lines of &#8220;<i>Lightroom needs to configure your system for the ..... plug-in.<\/i>&#8221;.<\/a>\n   <br\/>\n   <span class='meta'>\n     <a class='permalink' href='#configure'>permalink<\/a>\n     &middot;\n     Last Updated: Wed Apr 29 00:28:05 2015 UTC\n   <\/span>\n\n   <p>This is an issue with Lightroom's installer; the plugin does not need to be reinstalled.<\/p>\n\n<p>To fix it, either uninstall\/reinstall the Lightroom application, or\nopen a command window and run<\/p>\n<pre>\n    \"C:\\Program Files\\Adobe\\Adobe Lightroom Classic CC\\Lightroom.exe\" -register\n<\/pre>\n\n<p>You may need to run this as an administrator to get it to &#8220;stick&#8221;. Do\ninclude the quote symbols shown on the line above; also, you may need to\nadjust the drive name and folder path to match the location of your\nLightroom install. <\/p>\n\n<\/li>\n\n<li class='bodyq' id='baddownload'>\n   <a class='q2' >I can't install the plugin... I get various errors when I try to install it in the Plugin Manager<\/a>\n   <br\/>\n   <span class='meta'>\n     <a class='permalink' href='#baddownload'>permalink<\/a>\n     &middot;\n     Last Updated: Mon Apr  8 22:11:06 2013 UTC\n   <\/span>\n\n   <p>Did you follow <a\nhref='http:\/\/www.slrlounge.com\/boost-lightroom-4-performance-by-hacking-the-lightroom-modules-lightroom-4-workflow-system-dvd'>bad\nadvice<\/a> and actually remove some modules from your Lightroom app? Don't do that.\nReinstall Lightroom and try again.<\/p>\n\n\n<p>Next, check the upper-right section of the plugin manager.... are there any messages\nthere that give a hint?<\/p>\n\n<p>If not, then look in the lower-right section of the plugin manager...\nare there any diagnostics? If so, save them to a file and look at the\n<i>first<\/i> one (Lightroom shows the last one in the dialog, but only the\nfirst one has any meaning). If the message is about the inability to load a\nfile of some type, you likely have a corrupt download or corrupt unzip.\nSimply clicking on the download link on the plugin home page works fine for\nthe vast majority of people, but some small percentage of people get a\ncorrupt download. (I've heard of issues with Google Chrome not always\ndownloading properly, and of issues on 64-bit Windows 7, though most users\nin either case have no troubles.) Try a different browser to do the\ndownload, or a different utility to unzip the zip file.<\/p>\n\n<p>If none of this helps, drop me a note with details, such as what the\n<i>first<\/i> message of the lower-right diagnostics are, that you indeed\nchecked the upper-right section and found nothing, the versions involved\n(plugin and Lightroom), etc...<\/p>\n\n<\/li>\n\n<li class='bodyq' id='disappear'>\n   <a class='q2' >I had the plugin installed before, but suddenly it's missing... where did it go?<\/a>\n   <br\/>\n   <span class='meta'>\n     <a class='permalink' href='#disappear'>permalink<\/a>\n     &middot;\n     Last Updated: Mon Jul  5 23:26:36 2010 UTC\n   <\/span>\n\n   <p>Two possabilities come to mind: that you deleted the plugin from disk, or\nthat your Lightroom Preferences file has started to go corrupt. For the latter,\nsee <a href='#bad-preferences'>this FAQ<\/a>.<\/p>\n\n<p>If you deleted it from disk, just download and reinstall again,\nand try not to delete it this time :-).<\/p>\n\n<p>Part of the problem is that &#8220;installing&#8221; a plugin in Lightroom is really\njust letting Lightroom know where on disk the plugin resides, and Lightroom\nexpects to find it there from then on; Lightroom doesn't make a copy for\nitself, or anything like that. (This applies to all Lightroom plugins, by\nthe way, not just mine.)<\/p>\n\n<p>So, after downloading and unzipping the plugin, but before &#8220;installing&#8221;\nit into Lightroom's plugin manager, make move the <b>*.lrplugin<\/b> plugin\nfolder to where you'd like to keep it on disk. Most anywhere is fine as far\nas Lightroom is concerned, but it's best if it's a place that Lightroom can\nwrite to (that is, don't pick a place that requires administrator\nprivileges to install to if you're not going to be running Lightroom as an\nadministrator), because then the plugin can't update itself, leading to <a\nhref='#upgrade'>this problem<\/a>.<\/p>\n\n<\/li>\n\n<li class='bodyq' id='old-style-install'>\n   <a class='q2' >The &#8220;remove&#8221; button in the Plugin manager is grayed out, and I get an error when I try to upgrade.<\/a>\n   <br\/>\n   <span class='meta'>\n     <a class='permalink' href='#old-style-install'>permalink<\/a>\n     &middot;\n     Last Updated: Thu Mar 22 01:08:11 2012 UTC\n   <\/span>\n\n   <p>Lightroom provides for two ways to install\/manage plugins.<\/p>\n\n<p>The original (Lightroom 1) way to manage plugins in <span class='nobr'>Lightroom 1<\/span> was to place plugins into Lightroom's system plugin folder\n(<a href='https:\/\/regex.info\/blog\/2007-11-17\/638'>mentioned on this now-obsolete page<\/a>). You can still do that\nwith modern versions of Lightroom, but management of plugins installed this way &mdash; adding, removing, upgrading &mdash; must be done manually, via the file system\n(e.g. via Explorer or Finder). The only way to remove such a plugin is to remove it from the special plugin folder.<\/p>\n\n<p>Since Lightroom 2, the normal way <a href='https:\/\/regex.info\/blog\/lightroom-goodies\/plugin-installation'>to install a\nLightroom plugin<\/a> is to place the plugin somewhere on your drive where you don't mind leaving it (perhaps in a\n&#8220;Lightroom Plugins&#8221; folder you create in your home folder), then point Lightroom at it via the plugin manager's &#8220;Add&#8221;\nbutton. Users with multiple machines often keep their plugins on a shared <a href='https:\/\/www.dropbox.com\/'>Dropbox<\/a>\nfolder.<\/p>\n\n<\/li>\n\n<li class='bodyq' id='upgrade'>\n   <a class='q2' >I get an error when upgrading the plugin via the built-in &#8220;upgrade&#8221; button.<\/a>\n   <br\/>\n   <span class='meta'>\n     <a class='permalink' href='#upgrade'>permalink<\/a>\n     &middot;\n     Last Updated: Sun May 30 05:44:45 2010 UTC\n   <\/span>\n\n   <p>Yeah, it happens sometimes, sorry. Lightroom doesn't provide an upgrade\nsystem for plugins, so had to develop something myself, and it's greatly\nlimited by the plugin infrastructure. It seems to work for most cases, but\nit's not robust when faced with nonstandard machine setups.<\/p>\n\n\n<p>If you're on Windows, perhaps give a try to running Lightroom &#8220;as administrator&#8221;\n(from Explorer's right-click menu) for the upgrade.<\/p>\n\n<p>If in the end it doesn't work for you, please just do a normal manual\ninstall, as described on my <a\nhref='https:\/\/regex.info\/blog\/lightroom-goodies\/plugin-installation'>Lightroom\nplugin install page<\/a>. Before or after downloading\/unzipping\/installing\nthe new copy of the plugin, you can safely delete any old copies you have\non your local disk; all plugin settings and image data remains intact.<\/p>\n\n<p><b>If the plugin won't load after upgrading<\/b>, please try restarting Lightroom. I try to limit the need\nfor Lightroom restarts, but sometimes the way Lightroom loads plugins makes it required.<\/p>\n\n<\/li>\n<\/ul>\n\n\n\n<p class='h1'>General<\/p><ul>\n\n<li class='bodyq' id='packed'>\n   <a class='q2' >I sometimes get &#8220;Assertion failed: packed&#8221; when using your plugins<\/a>\n   <br\/>\n   <span class='meta'>\n     <a class='permalink' href='#packed'>permalink<\/a>\n     &middot;\n     Last Updated: Sat Jul 30 13:55:28 2016 UTC\n   <\/span>\n\n   <p>This seems to be a bug in Lightroom. I've reached out to Adobe.<\/p>\n\n<\/li>\n\n<li class='bodyq' id='mail'>\n   <a class='q2' >Why didn't you respond to my note about <i>(insert something unrelated to my plugins, tangential, or something already answered on my site)<\/i>?????<\/a>\n   <br\/>\n   <span class='meta'>\n     <a class='permalink' href='#mail'>permalink<\/a>\n     &middot;\n     Last Updated: Sun Sep  5 04:55:01 2010 UTC\n   <\/span>\n\n   <p>Sorry, but due to <a href='https:\/\/regex.info\/blog\/2010-09-18\/1620'>some arm\npain that limits my time on the computer<\/a>, I've had to make a change in\nmy priorities, and responding to emails and comments is now lower down on\nthe list. Sorry.\n<\/p>\n<\/li>\n\n<li class='bodyq' id='comparison'>\n   <a class='q2' >What's the difference between your upload-to-<i>xxxxxxx<\/i> plugin and the one of the same name that comes with Lightroom?<\/a>\n   <br\/>\n   <span class='meta'>\n     <a class='permalink' href='#comparison'>permalink<\/a>\n     &middot;\n     Last Updated: Sun Sep  5 04:55:01 2010 UTC\n   <\/span>\n\n   <p>The plugins that come with Lightroom are very bare bones; my plugins are\nmore complex, but have a lot more options, and also support normal\n(non-Publish) export as well. If your needs are very simple, the built-in\nplugins may be perfect for your needs. Give them a try.\n<\/p>\n<\/li>\n\n<li class='bodyq' id='avail'>\n   <a class='q2' >Do you have a plugin for uploading to <i>(insert name here)<\/i>?<\/a>\n   <br\/>\n   <span class='meta'>\n     <a class='permalink' href='#avail'>permalink<\/a>\n     &middot;\n     Last Updated: Sun May 30 05:31:22 2010 UTC\n   <\/span>\n\n   <p>If it's not listed on <a\nhref='https:\/\/regex.info\/blog\/lightroom-goodies'>my Lightroom goodies\npage<\/a>, then I haven't developed it, but that doesn't mean that someone\nelse hasn't. Check out Adobe's <a\nhref='http:\/\/www.adobe.com\/go\/lightroom_exchange'>Lightroom Exchange<\/a>\nfor lots of plugins and such.<\/p>\n\n<\/li>\n\n<li class='bodyq' id='log'>\n   <a class='q2' >I'm running into troubles with the plugin... is there a log or something I can send that might help you diagnose the problem?<\/a>\n   <br\/>\n   <span class='meta'>\n     <a class='permalink' href='#log'>permalink<\/a>\n     &middot;\n     Last Updated: Mon Jul 26 22:40:10 2010 UTC\n   <\/span>\n\n   <p>You can send the <b>plugin log<\/b> via the &#8220;Send to Jeffrey&#8221; button\nin the upper-right section of the plugin manager.<\/p>\n\n<p>Three important points to help me help you:<\/p>\n\n<ol><li><p>Do not email logs; use the submission feature. I can work with them better that way.<\/p><\/li>\n\n<li><p>If you're reporting about a problem that you can reproduce, please\nfirst clear the log (via the button next to the &#8220;Send to\nJeffrey&#8221; button, or by restarting Lightroom), and then do the minimum\nneeded to reproduce the problem... the fewest actions with the fewest\nphotos. The less activity in the log, the more likely I'll be able to zero\nin on the cause of the problem.<\/p>\n\n<p>Also consider enabling &#8220;Enhanced debug logging&#8221; prior to the test.<\/p><\/li>\n\n<li><p><b style='color:red'>Very Important:<\/b> The send-log dialog offers a place to add a\nnote to me. Please use it to describe why you're sending the log, <span style='color:orange'>even if\nyou've already told me via<\/span> email or a blog comment. I get a <i>lot<\/i> of\nlogs, and I have a very hard time keeping things straight, so giving me the\ninformation I need to debug things along with the log greatly increases the\nchances that I will not let it slip through the cracks.<\/p>\n\n<p>Where appropriate, full and exact names of specific files, urls, etc., help a lot.<\/p><\/li><\/ol>\n\n<p>There's also a separate, unrelated log kept by Lightroom, referenced in\nthe <b>lower<\/b>-right section of the plugin manager. If it reports more\nthan one diagnosis message, only the first is relevant: to access it, you\nhave to save the messages to a file, then open the file to view. If I ask for\nthese, please cut-n-paste them to an email or to the note box of the \n&#8221;Send to Jeffrey&#8220; dialog described above.<\/p>\n\n<hr align='left' width='20%'\/>\n\n<p id='crashlog'>If Lightroom is actually crashing, you can't use the &#8220;Send to\nJeffrey&#8221; button to send it because the act of restarting Lightroom clears the log.\nIn this case you have no choice but to find the log file, zip it up, and email it to me.\nThe log file is kept in a &#8220;*-log.txt&#8221; file named for the plugin, in the system's temporary folder.\n(When Lightroom is running, you can see the location via the &#8220;Show&#8221; button next to the &#8220;Send to\nJeffrey&#8221; button in the plugin manager.)<\/p>\n\n<\/li>\n\n<li class='bodyq' id='mogrify'>\n   <a class='q2' >About your LR\/Mogrify plugin, could you please...<\/a>\n   <br\/>\n   <span class='meta'>\n     <a class='permalink' href='#mogrify'>permalink<\/a>\n     &middot;\n     Last Updated: Mon May 31 01:11:45 2010 UTC\n   <\/span>\n\n   <p>That's not my plugin... <a\nhref='http:\/\/www.photographers-toolbox.com\/products\/lrmogrify2.php'>Lr\/Mogrify<\/a>\nwas written by <a href='http:\/\/timothyarmes.com\/'>Tim Armes<\/a>.\n<\/p>\n<\/li>\n\n<li class='bodyq' id='lion'>\n   <a class='q2' >I can't find my downloaded plugins in OSX Lion<\/a>\n   <br\/>\n   <span class='meta'>\n     <a class='permalink' href='#lion'>permalink<\/a>\n     &middot;\n     Last Updated: Tue Jul 19 02:51:53 2011 UTC\n   <\/span>\n\n   <p>If you had put them somewhere in your <b>~\/Library<\/b> folder tree, you'll find\nthat OSX Lion now hides that folder. See <a href='http:\/\/tarastips.net\/2011\/05\/show-hidden-library-folder-in-mac-osx-lion\/#comment-162'>this post<\/a>\nfor how to unhide that folder tree.\n<\/p>\n<\/li>\n\n<li class='bodyq' id='state'>\n   <a class='q2' >Why does the plugin sometimes fail with &#8220;The handle is in the wrong state for the requested operation&#8221;?<\/a>\n   <br\/>\n   <span class='meta'>\n     <a class='permalink' href='#state'>permalink<\/a>\n     &middot;\n     Last Updated: Mon Dec  3 08:57:20 2012 UTC\n   <\/span>\n\n   <p>This is a Windows-only Lightroom bug that affects Lr4.0, Lr4.1, and Lr4.2.<\/p>\n\n<p>I'm told that it has been fixed in Lr4.3, so please upgrade (see <span class='nobr'>&#8220;Help &gt; Check For Updates&#8221;<\/span> in Lightroom).<\/p>\n\n<\/li>\n\n<li class='bodyq' id='earth'>\n   <a class='q2' >In the Geoencoding Support plugin, the &#8220;<i>Geoencode selected photos from Google Earth<\/i>&#8221; feature doesn't work... it results in an &#8220;<i>Can't get location from Google Earth<\/i>&#8221; error.<\/a>\n   <br\/>\n   <span class='meta'>\n     <a class='permalink' href='#earth'>permalink<\/a>\n     &middot;\n     Last Updated: Mon Aug 17 10:32:45 2015 UTC\n   <\/span>\n\n   <p>It's a mystery why this feature doesn't work for some folks running\nWindows. Unfortunately, the behind-the-scenes method the plugin uses to\nacquire Earth's current location is no longer officially supported by\nGoogle, so if what used to work no longer works, there's not much we can\ndo.<\/p>\n\n<p>I've spent many hours trying to figure it out, without success. It works for most, but not for some. Frustrating.<\/p>\n\n<\/li>\n\n<li class='bodyq' id='republish'>\n   <a class='q2' >Photos keep showing up in &#8220;Modified Photos to Re-Publish&#8221; even though I didn't change anything.<\/a>\n   <br\/>\n   <span class='meta'>\n     <a class='permalink' href='#republish'>permalink<\/a>\n     &middot;\n     Last Updated: Sat Oct 29 03:07:16 2016 UTC\n   <\/span>\n\n   <p>This central feature of Publish has, unfortunately, never been reilable.\nI've submitted bug reports to Adobe for years, so far to no avail.\nSometimes photos just spontaneously move from &#8220;Published&#8221; to\n&#8220;Modified Photos to Re-Publish&#8221;, regardless of the settings in\n\u201cMetadata that Triggers a Republish\u201d and regardless of what's actually been\nchanged.<\/p>\n\n<p>If this bug strikes you, the best I can suggest is either:<\/p>\n\n<ol>\n<li><p>Just let the photos be republished if republishing doesn't hurt things.<\/p>\n\n<p>&#8220;Hurt things&#8221; could be that it takes up more time or CPU or bandwidth than you'd like.<\/p>\n\n<p>With Flickr, they don't allow videos to be republished, so you can't take this option in the first place.<\/p>\n<\/li>\n\n<li><p>Quietly move the photos back to &#8220;Published&#8221;.  Select the photos\nin &#8220;Modified Photos to Re-Publish&#8221; that you know haven't\nchanged (or, at least, that you know you don't mind not republishing),\nright click, and &#8220;Mark as Up-to-Date&#8221;.<\/p>\n\n<p>This can be done in bulk with the <a\nhref='https:\/\/regex.info\/blog\/lightroom-goodies\/bag-o-goodies#mark-up-to-date'>Mark\nSelected Publish Collections As Up To Date<\/a> fetaure of my Bag-o-Goodies\nplugin.<\/p><\/li>\n\n<\/ol>\n\n<p>One other thing to consider, if you just want to get some specific photos published without\nhaving to deal with others, is to select them and then hold down the Alt\/Option key. That\nturns the [Publish] button <span class='nobr'>into [Publish Selected],<\/span> which then\ndeals with just the selected photos.<\/p>\n\n<\/li>\n<\/ul>\n\n\n\n<p class='h1'>Network<\/p><ul>\n\n<li class='bodyq' id='handler'>\n   <a class='q2' >When trying to authenticate my login, my browser says it doesn't know how to handle &#8220;<b>lightroom:\/\/...<\/b>&#8221; links; what's wrong?<\/a>\n   <br\/>\n   <span class='meta'>\n     <a class='permalink' href='#handler'>permalink<\/a>\n     &middot;\n     Last Updated: Fri Jul  5 22:19:17 2013 UTC\n   <\/span>\n\n   <p>It looks like Lightroom's URL handler is not properly registered with\nyour OS. A reinstall of Lightroom should handle it.<\/p>\n\n<p>To re-install, first try &#8220;Help &gt; Check for Updates&#8221;,\nbecause you may as well make sure you're on the most recent version while\nyou're at it. Otherwise, perhaps visit Adobe to\n\n<a href='https:\/\/www.adobe.com\/cfusion\/tdrc\/index.cfm?product=photoshop_lightroom&amp;promoid&amp;promoid=DTEML'>download the latest version of Lightroom<\/a>.\n(The &#8220;trial version&#8221; is just the normal\nretail version without a serial number, which, if you already have, remains active across the reinstall.)<\/p>\n\n<p>Older versions of Lightroom (e.g. Lr5's latest) are available separately: \n\n<a href='http:\/\/www.adobe.com\/support\/downloads\/product.jsp?product=113&amp;platform=Mac'>Mac<\/a> &middot; \n\n<a href='http:\/\/www.adobe.com\/support\/downloads\/product.jsp?product=113&amp;platform=Windows'>Windows<\/a>.<\/p>\n\n<p>Creative-Cloud and Mac-App-Store users may need to reinstall differently, I don't know.<\/p>\n\n<\/li>\n\n<li class='bodyq' id='sec_error'>\n   <a class='q2' >I keep getting &#8220;Security Error&#8221; when trying to upload.<\/a>\n   <br\/>\n   <span class='meta'>\n     <a class='permalink' href='#sec_error'>permalink<\/a>\n     &middot;\n     Last Updated: Sun Jun  6 01:11:22 2010 UTC\n   <\/span>\n\n   <p>Nothing in Lightroom would generate this error natively... it's a problem outside of Lightroom and the plugin.\nI know of three possible reasons...<\/p>\n\n<ol>\n  <li><p>The date on your computer is off.\n      Secure networking doesn't work unless you have a reasonably accurate clock.\n      Check carefully... I've had people complain to me that their clock was correct,\n      when in fact it turned out to be exactly one day off, one month off, or one year off.\n      I kid you not.<\/p><\/li>\n\n  <li><p>You have some kind of security app prohibiting Lightroom from\n      using the network (in general, or to the specific site the plugin is\n      trying to upload to). Common examples are Little Snitch and Zone Defense.\n      You might try disabling them temporarily to check, but going forward you should be able\n      to add a Lightroom-specific exception.<\/p>\n\n      <p>Please check carefully...I can't tell you how many times people\n      have told me &#8220;I've disabled everything and I'm <i>still<\/i> getting\n      the error!&#8221;, only to come back a day or a week later and say &#8220;aaah, I\n      had forgotten about....&#8221;. <\/p><\/li>\n\n  <li><p id='zenfolio_security_error'>Your operating system's security support is out of date.<\/p>\n\n      <p><span style='color:red'>Zenfolio Users Nov 30, 2017:<\/span><\/p>\n\n      <p>In particular, OSX (now called &#8220;MacOS&#8221;) didn't include some important security support until\n      two years ago with <span class='nobr'>OSX 10.11 (&#8220;El Capitan&#8221;),<\/span> so Lightroom running on\n      <span class='nobr'>OSX 10.10<\/span> and prior won't work with secure web sites that enforce now-common\n      minimum levels of security. For example, Zenfolio started requiring this level of security support in late Nov 2017.\n      In order to upload to Zenfolio with Lightroom on a Mac, one must upgrade to OSX 10.11 (released in 2015) or later.\n Here's\n<a href='https:\/\/www.zenfolio.com\/us\/z\/help\/support-center#\/customer\/en\/portal\/articles\/2361556-how-to-use-jeffrey-friedl-s-lightroom-plugin'>Zenfolio's note on the issue<\/a>.<\/p>\n\n      <p>(As an aside, many web browsers don't rely on the underlying operating system for their security support,\n      so they can still be used to upload even without upgrading the operating system.)<\/p>\n\n      <p><b>[SmugMug only]<\/b> &mdash; if you get &#8220;securityError&#8221; with SmugMug, you need to install a particular\n      SSL cert to work with SmugMug's API servers: Download the &#8220;Starfield Class 2 Certification Authority Root Certificate&#8221;\n      <a href='http:\/\/certs.starfieldtech.com\/repository'>from here<\/a>, double-click to install, and restart Lightroom.<\/p>\n\n   <\/li>\n\n<\/ol>\n\n<\/li>\n\n<li class='bodyq' id='networking'>\n   <a class='q2' >I keep running into networking errors (&#8220;Unexpected reply...&#8221;, &#8220;no reply...&#8221;, &#8220;timeout...&#8221;, etc.)<\/a>\n   <br\/>\n   <span class='meta'>\n     <a class='permalink' href='#networking'>permalink<\/a>\n     &middot;\n     Last Updated: Thu Sep 27 22:48:01 2012 UTC\n   <\/span>\n\n   <p>It's almost certainly not specifically related to the plugin or even\nLightroom, so there's not much I can do but to suggest the standard things:<\/p>\n\n<ul>\n<li>If you're on Windows, be sure to disable &#8220;SSL 3.0&#8221;. <a href='http:\/\/photos.smugmug.com\/photos\/i-JshSsXB\/0\/X3\/i-JshSsXB-X3.png'>See here<\/a> for instructions.<\/li>\n\n<li>Make sure you don't have some kind of security app interfering with Lightroom's networking. You may need to add exceptions with each major version of Lightroom.<\/li>\n<li>Reboot your router \/ computer.<\/li>\n<li>Make sure your system clock is set accurately.<\/li>\n<li>It could be your ISP or the upload destination is having &#8220;issues&#8221;, so perhaps you just need to give it time.\n(Many upload services have different upload endpoints between their own web-based uploads and the 3rd-party API that plugins use, so it's possible their API could be having issues while their web-based tools continue to work, and vice-versa.)<\/li>\n<\/ul>\n\n<p>Larger uploads obviously increase the exposure to networking errors and\ntimeouts, so consider at least testing with smaller uploads. One way to\nmake a smaller upload is to use a lower JPEG quality setting. For example,\nas <a\nhref='https:\/\/regex.info\/blog\/lightroom-goodies\/jpeg-quality'>described\nhere<\/a>, a quality setting of 93 doesn't usually represent a perceptibly\nbetter image than a quality setting of, say, 77, but the resulting upload\ncan be a good 4&times; larger(!)<\/p>\n\n<p>Another way to reduce the upload size is to lower the pixel-size of the\nupload in the Image Sizing section of the Export\/Publish dialog.<\/p>\n\n<p>Also, do make sure you're using the latest version of Lightroom.<\/p>\n\n<\/li>\n<\/ul>\n\n\n\n<p class='h1'>Registration<\/p><ul>\n\n<li class='bodyq' id='cc_reg'>\n   <a class='q2' >With my new Creative-Cloud install, I can't register my plugins because instead of the registration button the Plugin Manager shows \"<i>Plugin registration button appears here after Lightroom is registered with Adobe<\/i>\".<\/a>\n   <br\/>\n   <span class='meta'>\n     <a class='permalink' href='#cc_reg'>permalink<\/a>\n     &middot;\n     Last Updated: Thu Jun 26 01:55:12 2014 UTC\n   <\/span>\n\n   <p>Please update the plugin to the latest version, and it should work.\n(Updated July 8th, 2014)\n<\/p>\n<\/li>\n\n<li class='bodyq' id='reg_code'>\n   <a class='q2' >I generated a transaction at PayPal (see, here's my PayPal receipt as proof)... when will you send me the registration code?<\/a>\n   <br\/>\n   <span class='meta'>\n     <a class='permalink' href='#reg_code'>permalink<\/a>\n     &middot;\n     Last Updated: Sun May 30 05:06:11 2010 UTC\n   <\/span>\n\n   <p>The registration code is in the PayPal receipt (the <b>Unique Transaction\nID<\/b> or the <b>Receipt Number<\/b>, <a\nhref='https:\/\/regex.info\/blog\/lightroom-goodies\/register#example'>as\nillustrated here<\/a>.\n<\/p>\n<\/li>\n\n<li class='bodyq' id='reg_server_connect'>\n   <a class='q2' >When I try to register from within the plugin, I get a &#8220;<i>Can't contact Jeffrey's server<\/i>&#8221; error.<\/a>\n   <br\/>\n   <span class='meta'>\n     <a class='permalink' href='#reg_server_connect'>permalink<\/a>\n     &middot;\n     Last Updated: Sun May 30 05:06:11 2010 UTC\n   <\/span>\n\n   <p>If you're reading this on my site, my machine is up and working, so the problem is almost certainly some\nsecurity\/firewall setting on your machine (Zone Defense? Little Snitch? Norton?) blocking Lightroom from connecting to\nmy machine. Please check your settings, and perhaps add an exception to allow Lightroom to freely use the network.<\/p>\n\n<p>If you try to connect with your browser and get a\nsecurity-warning error, check your system clock. It must be reasonably accurate for any https\/ssl to work. You would be\nshocked at the number of people who complain to me about things not working when it turns out that their system clock is\none month or one year off.<\/p>\n\n<\/li>\n\n<li class='bodyq' id='rc'>\n   <a class='q2' >The plugin says &#8220;<i>Plugin registration button appears after Lightroom is registered with Adobe.<\/i>&#8221;, but Lightroom doesn't give me a place to enter my Lightroom  serial number.<\/a>\n   <br\/>\n   <span class='meta'>\n     <a class='permalink' href='#rc'>permalink<\/a>\n     &middot;\n     Last Updated: Tue May 22 03:34:13 2012 UTC\n   <\/span>\n\n   <p>I bet you're an &#8220;RC&#8221; (&#8220;Release Candidate&#8221;) version of Lightroom. For some reason, they don't\nlet you enter your Lightroom serial number.<\/p>\n\n<p> It's a hassle, but the best I can think of is to downgrade temporarily\nto the non-RC version; for example, if you're running a\nLr6.1RC, reinstall Lr6.0\nfrom <a href='http:\/\/www.adobe.com\/products\/photoshoplightroom\/'>Adobe's\nmain Lightroom site<\/a> and enter your serial number into that one. Then go\nback and reinstall the RC, and the serial will already be there, so you can\nthen register plugins.<\/p>\n\n<\/li>\n\n<li class='bodyq' id='upgrade_registration'>\n   <a class='q2' name='lr3_registration'>My plugin registration code doesn't work after upgrading Lightroom to the latest major release.<\/a>\n   <br\/>\n   <span class='meta'>\n     <a class='permalink' href='#upgrade_registration'>permalink<\/a>\n     &middot;\n     Last Updated: Sat Jul  3 03:31:20 2010 UTC\n   <\/span>\n\n   <p>Yeah, sorry about that. A side effect of the registration system I built\nis that <i>major<\/i> upgrades\n\n  <span class='nobr'>like Lr5 &rarr; Lr6<\/span>\n\n (but not <i>minor<\/i> upgrades\n\n  <span class='nobr'>like 6.0 &rarr; 6.1)<\/span>\n\n cause plugins to become unregistered. As described\n<a href='https:\/\/regex.info\/blog\/lightroom-goodies\/register#major-upgrade'>on the registration page<\/a>,\nyou can just generate new codes with 1-cent transactions if you like. It's a hassle, I know. sorry.<\/p>\n\n<\/li>\n\n<li class='bodyq' id='bad-preferences'>\n   <a class='q2' >I registered the plugin before, but now it's not registered... what happened?<\/a>\n   <br\/>\n   <span class='meta'>\n     <a class='permalink' href='#bad-preferences'>permalink<\/a>\n     &middot;\n     Last Updated: Thu Oct  4 00:45:13 2012 UTC\n   <\/span>\n\n   <p>Most reports I get of this are because of three things: a Lightroom major-version upgrade (see the previous question),\nconfusion about which plugin was registered, and a corrupt Lightroom-preferences file.<\/p>\n\n<p>In case of the second one, pay careful attention to messages to see\nwhich plugin is and isn't registered. My plugins tell you clearly in the\nPlugin Manager.<\/p>\n\n<p>If a plugin becomes unregistered due to Lightroom preferences becoming\ncorrupt, you can try to reregister it (if you're not using a Creative-Cloud\ninstall, try the &#8220;forgot your code?&#8221; button in the registration\ndialog to automatically bring up your code for the current plugin and the\ncurrent Lightroom serial number), and hope it &#8220;sticks&#8221; across\nthe next Lightroom restart, but if it doesn't, you'll have to wipe your\nLightroom preferences file and so that Lightroom can rebuild it when it\nnext launches.<\/p>\n\n<p>For info about how to reset your preferences, <a\nhref='http:\/\/www.lightroomqueen.com\/articles-page\/how-do-i-reset-lightrooms-preferences\/'>see\nthis page<\/a> or <a\nhref='https:\/\/helpx.adobe.com\/lightroom\/kb\/preference-file-and-other-file-locations---lightroom-6.html'>this\nAdobe help page<\/a>.<\/p>\n\n<p>After you then start Lightroom and it creates a new preferences file for\nyou, all your photo-related data remains unchanged, but many little\npersonal settings (such as the default catalog to work with, the widths of\nthe panels, etc.) will have reverted to their defaults. Depending on how\nmuch you've customized things, it can be a hassle to set things back up the\nway you like. )-:<\/p>\n\n<p>You'll also have to re-tell Lightroom about the plugins you had\ninstalled. Visit the plugin manager and point the &#8220;Add&#8221; button\nat each plugin you had installed, and if they had been registered, re-enter\nthe registration code as described above.<\/p>\n\n<\/li>\n<\/ul>\n\n\n\n<p class='h1'>Uploading<\/p><ul>\n\n<li class='bodyq' id='cookies'>\n   <a class='q2' >I get a &#8220;missing destination cookies&#8221; error when trying to publish.<\/a>\n   <br\/>\n   <span class='meta'>\n     <a class='permalink' href='#cookies'>permalink<\/a>\n     &middot;\n     Last Updated: Sun Oct 14 14:32:19 2012 UTC\n   <\/span>\n\n   <p>This rare error is caused, as best as I can tell, by an error in\nLightroom that causes it to lose\/forget important plugin data. I've never\nbeen able to track it down, but the end effect is that all the data the\nplugin saved about a particular Publish Collection has been ripped out from\nunder the plugin, leaving it with no way to continue.<\/p>\n\n<p>The only way to recover is to delete the Publish Collection, then\nrecreate it. The &#8220;Populate&#8221; feature of my Publish plugins can allow you to\nrecreate it quickly and easily, though it's somewhat of a fragile\nprocesses.<\/p>\n\n<p>It's unknown what causes Lightroom to suddenly lose this catalog data,\nbut it's possible that it's simply one manifestation of wider catalog\ncorruption, so it's prudent to perform a backup and integrity check on the catalog.\nTo do this, visit <span class='nobr'>&#8220;<b>Lightroom &gt; Catalog Settings...<\/b>&#8221;<\/span>\nand at the bottom of the General tab, set &#8220;Back up catalog&#8221; to &#8220;When Lightroom\nnext exits&#8221;, then exit Lightroom. That will cause the backup dialog to appear.\nBe sure to enable the &#8220;Test integrity before backing up&#8221; option. It doesn't hurt\n(and likely helps general Lightroom responsiveness) to also enable &#8220;Optimize catalog after backing up&#8221;).<\/p>\n\n<p>The automatic backup selection that you put to &#8220;When Lightroom next\nexits&#8221; will revert back to whatever it was before. If it had been &#8220;Never&#8221;,\nperhaps take this opportunity to set it to make occasional backups. It's\nalso prudent to back up all the myriad of Lightroom's ancillary\nconfiguration and preset files, so consider <a\nhref='http:\/\/photographers-toolbox.com\/products\/mdawson\/tpglrbackup\/'>Matt\nDawson's <i>LR Backup<\/i> plugin<\/a>.<\/p>\n\n<\/li>\n\n<li class='bodyq' id='corrupt-settings'>\n   <a class='q2' >I get a &#8220;corrupt collection settings&#8221; error when trying to publish.<\/a>\n   <br\/>\n   <span class='meta'>\n     <a class='permalink' href='#corrupt-settings'>permalink<\/a>\n     &middot;\n     Last Updated: Mon Sep  2 23:12:32 2013 UTC\n   <\/span>\n\n   <p>This is the same underlying problem as the &#8220;<a href='#cookies'>missing destination cookies<\/a>&#8221; problem above,\nwith the same frustrations and the same potential workarounds.\n<\/p>\n<\/li>\n\n<li class='bodyq' id='new-smugmug'>\n   <a class='q2' >The SmugMug plugin won't let me set the image <i>Caption<\/i> and other &#8220;New SmugMug&#8221; things<\/a>\n   <br\/>\n   <span class='meta'>\n     <a class='permalink' href='#new-smugmug'>permalink<\/a>\n     &middot;\n     Last Updated: Mon Sep  2 23:12:32 2013 UTC\n   <\/span>\n\n   <p>SmugMug has not yet updated its third-party API for their summer-2013 redesign, so there's not much I can do\nbut wait. I hear that SmugMug's own plugin may already handle the new redesign, but \n<a href='http:\/\/help.smugmug.com\/customer\/portal\/articles\/93281'>their plugin's home page<\/a> still documents\nthings as of <span class='nobr'>Lightroom 3<\/span> (circa a couple of years ago), so it's hard to tell.\n<\/p>\n<\/li>\n\n<li class='bodyq' id='original'>\n   <a class='q2' >I don't see Lightroom editing changes in the copies uploaded to <i>online photo-hosting service<\/i>...<\/a>\n   <br\/>\n   <span class='meta'>\n     <a class='permalink' href='#original'>permalink<\/a>\n     &middot;\n     Last Updated: Tue Aug 19 04:31:14 2014 UTC\n   <\/span>\n\n   <p>Check the &#8220;File Settings&#8221; section of the Export\/Publish dialog, and ensure that &#8220;Image Format&#8221; is <b>not<\/b> set to &#8220;Original&#8221;. That's because &#8220;Original&#8221; does <b>not<\/b> mean &#8220;the same format as the original master image&#8221; as might seem obvious.... \nAdobe has inexplicably made &#8220;Original&#8221; mean \"The original pixels from the master image file (without any Lightroom changes), but with new metadata from your catalog\".<\/p>\n\n<p>I have no idea how this is useful or desired, but that's how it is. You probably want &#8220;Image Format&#8221; to be &#8220;JPEG&#8221;.<\/p>\n\n<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>This page covers the answer to common questions that I (Jeffrey Friedl, an American software guy and hobby photographer in Kyoto) get about my plugins for Adobe Lightroom. Most days, it seems, I spend more time answering emails than I do developing new features or fixing bugs, so this page is an attempt to become a bit more efficient all around.<\/p> <p class='h1'>Installing<\/p> I get \"An error occurred while reading the schema for the plug-in. The plug-in will be disabled.\" What's wrong?Every time I start Lightroom, I get a message long the lines of \"Lightroom needs to configure your system [...]","protected":false},"author":1,"featured_media":0,"parent":864,"menu_order":0,"comment_status":"open","ping_status":"open","template":"","meta":{"footnotes":""},"_links":{"self":[{"href":"https:\/\/regex.info\/blog\/wp-json\/wp\/v2\/pages\/1535"}],"collection":[{"href":"https:\/\/regex.info\/blog\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/regex.info\/blog\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/regex.info\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/regex.info\/blog\/wp-json\/wp\/v2\/comments?post=1535"}],"version-history":[{"count":0,"href":"https:\/\/regex.info\/blog\/wp-json\/wp\/v2\/pages\/1535\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/regex.info\/blog\/wp-json\/wp\/v2\/pages\/864"}],"wp:attachment":[{"href":"https:\/\/regex.info\/blog\/wp-json\/wp\/v2\/media?parent=1535"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}