digifiend, having bitten before by strange zip setups, I actually went in and unzipped it, then located the modules/eeflickr folder and uploaded that to my my modules folder; then I found the lang.* files and uploaded those to the language/english folder. You might want to give that a shot, as I suspect things didn’t end up quite where they should have. =)
(Meanwhile, I’ve moved this from the Plugins forum =) )
I figured out the issue, and I am officially a bonehead. It turns out that I have a system subdirectory in addition to the subdirectory that contains the live system files (no I dont know why). So it turns out that I had copied the files to a dead subdirectory. Works great when copied to the right place.
I’m looking forward to making a test page and trying this out
Ive played around with this and it works great for pulling either set or pic data from a set. What I am really having problems with is visualizing and templating an initial page with set listings (pic over title), allowing somebody to click on a set, have the pics for that set pop open, and a mechanism to display the selected pic.
In other words, how does the selected set id from exp:eeflickr:photosets_getList get passed into the exp:eeflickr:photosets_getPhotos? Are there any sample templates out there that might explain typical usage?
It gets done by segment. So, for instance, the photosets_getList has a set of variables, one of which is {id}, you create a link passing {id} into the last segment, then on your single entry page, pull that in using the appropriate parameter (which I don’t know off-hand). you can use the same method to call in comments on that photo; but there is no tag to leave comments, or I would be doing that on my site too.
It gets done by segment. So, for instance, the photosets_getList has a set of variables, one of which is {id}, you create a link passing {id} into the last segment, then on your single entry page, pull that in using the appropriate parameter (which I don’t know off-hand). you can use the same method to call in comments on that photo; but there is no tag to leave comments, or I would be doing that on my site too.
You’d think that I’d know about segmenting by now, but nope. After passing the id in the URL, I have successfully created a page with all the sets and a page that displays a particular set. Of course, it doesnt look good because none of the css is in place, but I think the hard part is behind me.
Hey you got it! It’s pretty neat, eh? And you learned about one of the more powerful tools in EE’s arsenal; a good day, I say. =) Glad I was able to help, the module is new to me, too. =)
and the part about leaving comments.. well the complication is that in order to leave a comment each user must be independently authenticated to the API not just the module itself. so in order to use the API to post a Comment Flickr would have to ask each user if it was ok first (also provided they are a Flickr Member) then the user could post a comment using the API based on that session. Right now the Module if authentication is setup just authenticates itself to Flickr as if it were the API key’s owner. so i could use the cpmment post methoud but all comments would be posted as if they came from you.
as a standalone process individual user auth is pretty easy but i really wanted to find a way to wrap that into the EE user registration. and i have not yet begun to look into that. hopefuly it will be as simple as asking in the member cp what there flickr “nsid” is or “username” is, then a flickr allow window would open the user says “ok” and then they are logged in.
but it would add a new level of functionality allowing you to show photos ect. based on each users contact level (friend, family, contact, anonymous) and also mix that with user groups in EE. but i really wanted to get what i consider the core API methods debugged first.
another way for comments would be to have eeFlickr wright each images id to a weblog treating each image as a weblog entry and then have on site commenting based on that and not the flickr API
lumis - I did not mean to criticize; I implemented eeFlickr over the weekend and was really extremely impressed with it. You have some really great ideas for it and it’s working brilliantly now. However, since you’re here, might I ask one question? Do you know, off-hand, the default Flickr cache refresh? You mention it in the docs, but I’ve had to add refresh= to all of my tags to get new images to show up. It’s only at a 60 minute refresh and I would have thought the API itself would be that at minimum.
It’s really an amazing module; I love the idea of having it write to entries and also remote commenting, I’m torn about which I’d use if given a choice. I just love that the module itself works so well and so transparently with EE’s own methodology.
Lisa
i did not take it as criticism it is something that makes my forehead squinch up when i think about how to deal with commenting. and also photo uploading but i guess thats a good thing.
one thing i have tried to do with this is follow the API and try not to put my own output methods in the module. the “tag cloud” stuff is where i did put some of my own stuff in but i thought it called for it there.
the default cache refresh in the module is 1 day. (i plan on adding a clear cache button and a update time option to the module CP) if you did not cache the data flickr would return the data fresh every time you ask for it, which would slow down your site considerably depending on which tags you were using and how you nest them. When i building my templates i just set refresh=“1” until i was done.
I use both eeFlickr’s cache and EE template caching once i got my html the way i wanted it. and the load is very fast and since each tag is cashed independently depending on the prams passed. different pages once the cache expires will update at different times. because chances are there is not someone loading every page of your site at the same time. Reused tags on multipul pages are only cached by eeflickr once so there is no overhead on using the same tag with the same params on many templates or many times in the same template.
my first crack at the flickr api was a standalone PHP app that i modeled off of EE’s url segment variables and template system. however i slapped myself around one day asking why am i trying to re-invent this. thats where the module came in.
lumis, thank you for expanding on that. The refresh being 1 day makes perfect sense, and I did as you do and set it to 1 until I was done. I have it at 60 right now as I’m still setting up the flickr end, but will likely set it to 120 once that’s done. 12 calls a day; seems reasonable, I think.
I need to dig into the tagging aspects, I haven’t gotten there yet. I still want to set up entry-image relationships using a custom field, passing the information by embed, so I can store those images on flickr. I also like it that you’re using segments because I am envisioning that this may allow me to call in flickr images based on tags at the same time that I call in my entries based on the Tag module tags. I still have some features to add, but this module is definitely making things easier.
This module is fantastic. I almost have it working exactly how I want it, but I have run into a snag. I’m not sure where to post the snag (it has to do with retaining info retrieved via segmenting) but it’s directly related to this module. So is this question a module question or a general “how to” question?
I say ask it here, especially since lumis is watching; I can always split it off if it ends up being a general EE question. You can also isolate if that is the case by hardcoding the variable to test and if it works, then try the segment approach. I admit I’m curious though.
I say ask it here, especially since lumis is watching; I can always split it off if it ends up being a general EE question. You can also isolate if that is the case by hardcoding the variable to test and if it works, then try the segment approach. I admit I’m curious though.
This may not be that interesting as I may (yet again) be missing something very basic. But here I go.
On what will be my main photo page (http://digifiend.com/index.php/site/test), I have successfully created a page with all of my flickr sets. Clicking on a set (lets take the 200710-Maine photoset, top left corner) successfully retrieves small sized thumbnails of all the pics in the set. In segment 3, the set number appears, and in segment 4, the word photoset appears (http://digifiend.com/index.php/site/test1/72157602564394884/photoset).
Now the goal will eventually be to have a larger pic on the right hand side of the page displayed when one of the pics on the left is selected. This will be done via an <a href> with the set number in segment 3 (to retain the set thumbnails), and a photo number in segment 4 (replacing the temporary photoset keyword).
I’m having a problem on figuring out how to retain the set number. Since the exp:eeflickr:photosets_getPhotos function doesnt have a mechanism to actally pass the set id (which probably wouldnt make much sense), I can’t figure out how to harvest and reissue the segment which was previously assigned by the exp:eeflickr:photosets_getList {id} variable.
The ultimate goal is to have the initial URL to the page which calls a specific set of images be /72157602564394884/photoset and have any pictures selected change segment 4 so the URL looks like 72157602564394884/1161197623.
Does this make sense? Is there a better way to do this?
Hey, DF - my folks were in town this weekend and I’ve had no time to pop back into the forums until now. I"m glad you were able to get this worked out, because I was having some trouble following and was about to ask for the template code. =)
No worries, I guess I sometimes have problems grasping when to use quote marks and when they aren’t necessary. I’m pleased with the layout, I just need to make some basic decisions on how I want to style it all.
Hope the visit with the ‘rents went well, I never know how that will go with me until it happens
