Copy link to clipboard
Copied
Hi,Guys,,yesterday,I,was,trying,to,post,an,image,from,Lightproof,Classic,CC,to,instagram.,I,now,keep,on,getting,a,message,saying,"attempted,to,index,field,media,(a,nil,value),(1).,It,is,very,frustrating,as,I,have,absolutely,no,idea,what,is,going,on.
Copy link to clipboard
Copied
A number of people have reported that the most recent version of the LR/Instagram plugin (0.6.1575) fixes the recent problems people have been having:
LR/Instagram plugin just starting giving an error
Re: LR/Instagram plugin params load error while trying to publish a photo ​
Copy link to clipboard
Copied
John, thanks for the info. I have reloaded the latest plugin and now getting an error message http status 408 (1). Any ideas on this one. It is driving me crazy!!!!!
Copy link to clipboard
Copied
Status code 408 ("Request Timeout") could be sent as the result of a number of conditions: The network connection to Instagram became very slow or unresponsive, there's a software problem at Instagram that caused its server to think the plugin or network was too slow, the plugin has a problem in sending a complete request to Instagram, or a problem in LR delayed the plugin from sending a complete request.
I recommend rebooting your LR, restarting your network router/modem, and if it still occurs, waiting a day to see if it's an Instagram problem that will clear up. If at that point you still see it, contact the plugin developer at his Web site.
Copy link to clipboard
Copied
I’m having the same issue running classic cc 7.5 release export results ?:0 attempt to index field ‘media’ (a nil value) (2)
it goes half way through export stops and gives me this message
Copy link to clipboard
Copied
In File > Plug-In Manager, verify you are actually running the most recent version of the LR/Instagram plugin(0.6.1577). Make sure any old versions are removed from Plug-In Manager. It looks like this most recent version is trying to better handle Instragram's new user authentication protocol introduced in September (according ot the plugin author), which is causing these various errors.