Home › Forums › Publish on Gallery 3 › Unhandled Exception when Download Album Info
This topic has 2 voices, contains 17 replies, and was last updated by 
| Author | Posts |
|---|---|
| Author | Posts |
| February 7, 2012 at 5:23 pm #1259 | |
 Hammers | Tomek, Thank you for these modules. I greatly appreciate your work. Also, thank you for adding the caption to title option for XMP. I am having difficulty with POG3. When I enter the information and try to Download Album Info, I get an Exception. Please see these screenshots: Here is the debug information: ************** Exception Text ************** ************** Loaded Assemblies ************** ************** JIT Debugging ************** For example: When JIT debugging is enabled, any unhandled exception I am running the client side application on Windows 7 64-bit. This is a new install of Gallery 3 with my Gallery 2 albums imported into it. Any ideas what I am doing wrong? HammersQuote |
| February 9, 2012 at 10:28 am #1264 | |
 Tomek | Hi, I will take a look at this over the weekend when I have some more time. In the mean time, would you also mind noting down which (if any) non-default Gallery 3 modules you are running (aside from XMP)? Do you have any “odd” names for your photos or albums? By that I mean non-English lettering, or perhaps some html code in your album names? There are also non PoG ways of testing whether things will work right, if you have a way of changing the headers sent to your website (something like modify headers for Firefox) and you’re feeling a little adventurous. That might at least give use what PoG is trying to parse and failing. Thanks, Tomek EDIT: I forgot to say thank you for a thorough bug report – it’s much easier to get the screenshots and the stack trace at once! TomekQuote
|
| February 9, 2012 at 6:11 pm #1267 | |
| Hammers | Tomek, I currently have several modules installed, but I had less modules installed when I originally test it. My album names are all pretty generic. I don’t have any high-level ascii characters, characters with accents, or anything strange. No HTML in character names. I think if you look at the forums for POG2 you will see several users post a similar-looking problem. I am wondering if it has something to do with failing authentication? But that is nothing more than a guess. I can do some header testing with Firefox if you’re willing to provide detailed instructions. I’m not really much of a web developer. I’m just a guy that is handy with computers. I don’t mind experimenting with firefox. I can spin up a VM and make any changes without worrying about breaking something. Thanks, HammersQuote |
| February 12, 2012 at 12:52 am #1269 | |
| Tomek | Hi Ken, I think I might need you to try some debugging with headers. None of those plugins are ringing any bells for me. Basically, I think the error you see is from the program choking on trying to interpret information sent back from your Gallery3 Install. Please download the “Modify Headers” add-on for Firefox. Enable it, and add the following two headers using “Add” button: 1) X-Gallery-Request-Key – This is your REST key that you would use for the Publish on Gallery authentication key. Enable the two keys you just set up, and make sure to hit the “start” button on the add on itself. Once you have that loaded, go to “http://YOUURL.com/gallery3/rest/item/1?type=album&output=html”. You should see what looks like list of information about your root album. If you see only “[ ]” that usually means that you don’t have the right headers set up. You can check that you are correctly sending the headers by opening up Firefox’s web console (ctrl+shift+k), reloading the page, and then clicking on the underlined URL after “GET”. You should see both of your “X-Gallery-Request-XYZ” headers listed. If the page loads correctly, one of the items listed should be the “members” of that album. This should be something like: ‘members’ => If you could email me the entire contents, not just the members, of the page you see (email: my first name at the url of this site), so I can take a closer look, that would be great. I’m asking by email, since I really need the full output, and it might contain private info. While we’re at it, could you double check that you have .NET 4.0 installed on your Win7 machine? And could you let me know which version of Gallery3 you have installed? (By going to the admin dashboard, it should be on the top right under gallery stats. Could you give the full version including build number?). Hopefully we can get this squared away! Tomek TomekQuote |
| February 12, 2012 at 11:08 am #1270 | |
 T Jones | I had the same error. I have used this many times. I then realized that I changed the website address and not the user API. All errors disappeared. I now know one API for each website address and user. I don’t know if this error relates to API but my error had the same headings. Thank you for such and easy way to publish. I will definitely give to your coffee fund. T JonesQuote |
| February 12, 2012 at 12:57 pm #1272 | |
| T Jones | FYI Hope this helps others. T JonesQuote |
| February 13, 2012 at 12:07 pm #1273 | |
| Hammers | Tomek, I don’t think it worked as intended. I installed the plugin and loaded the header options. I clicked start and entered the URL into a browser tab. I think the problem is that URL doesn’t exist. Anytime I enter a URL that doesn’t exist, my browser will just default back to my homepage. That is what happened here. I hope that test provided you with something meaningful that you can use and that I didn’t mess something up. Let me know what you’d like me to try next. HammersQuote |
| February 13, 2012 at 12:07 pm #1274 | |
| Hammers | |
| February 13, 2012 at 1:46 pm #1275 | |
| Tomek | Ahh, we’re getting closer then. I actually double checked on your gallery with /gallery3/index.php/rest/item/1, and got the answer I expected (nameley “[]“). Come to think of it, I could’ve done this myself earlier…sorry for leading you on a wild goose chase. You could go there and see what I was talking about. The actual content isn’t important any more. However, this most likely means that your rewrite rules for URL’s aren’t set up in the (I think) default Gallery3 setup. In the gallery3 install folder, there should be an ‘.htaccess’ file, that contains a section that looks like “mod_rewrite”. What I have is here: http://kott.fm/tomek/forums/topic/patch-problem-with-mod_rewrite/#post-1126. If you could post that section of your configuration, we can probably figure out a way to get things working. I have a feeling that it was my last bugfix in PoG that actually caused this, since to be more accommodating of other “mod_rewrite” configurations, I got rid of “index.php” as part of the default URL that it checks. Perhaps the better way to do this is to provide a second check, in case the “/rest/item/1″ URL doesn’t work, to fall back onto “index.php/rest/item/1″. I’ll try to code that up this week or weekend, and release a new version of PoG. TomekQuote |
| February 13, 2012 at 2:16 pm #1277 | |
| Hammers | Tomek, Thanks for getting back so quickly. I don’t have an .htaccess file in my gallery3 folder. Actually, I don’t have one in my gallery folder, either. The only .htaccess file I have is in the root of my website in the ‘kenaldrich.com’. folder. It looks like I’m just using the default one that came with Joomla. Maybe I should be doing things much differently? I barely know what I’m doing here, haha. Details below: ## ##################################################### ## Can be commented out if causes errors, see notes above. # RewriteEngine On ########## Begin – Rewrite rules to block out some common exploits # Uncomment following line if your webserver’s URL # RewriteBase / ########## Begin – Joomla! core SEF Section HammersQuote |
| February 13, 2012 at 2:33 pm #1278 | |
| Tomek | Huh, it’s odd that you don’t have an .htaccess file for the gallery3 install. I’m surprised things are even working to show the pages! The file should come with the downloaded package; I just double checked to make sure I wasn’t wrong on that. I think the easiest thing to do is to check your downloaded gallery3 install, and copy that .htaccess over to your gallery3 folder (i.e., don’t overwrite the one provided by joomla in the root folder). You’ll then have to uncomment some of the lines at the bottom of that file, and change the “RewriteBase” to “/gallery3″ (and then eventually to “/gallery” once you switch over). Basically, a “.htaccess” file provides some directions for the web server that are configurable by the end user (you) rather than for the entire server (which on a shared server might be many many people). You can provide one in each and every directory. The directions are cumulative, with child folders (such as gallery3) directions overriding parent ones (such as your root). Tomek TomekQuote |
| February 13, 2012 at 4:35 pm #1279 | |
| Hammers | Tomek, Thanks. I just re-downloaded Gallery 3 and unzipped it on my windows workstation. Sure enough, there is an .htaccess file. I went to make the changes to the file and save it, but windows would net let me. The file begins with a period. I suspect this is what caused my problem when I originally copied gallery 3 to my server. Instead of copying the archive to the server and decompressing there, I had unzipped here and uploaded the uncompressed version. I suspect Windows had a problem with that file because of the period at the beginning of the name. So, I just modified the file, saved it as a text, put it in gallery3 folder, and opened a shell with putty to rename it. Now Firefox is behaving as you had instructed it would earlier. I now see the members array. I tried the POG3 plugin through WLPG and still got an exception, but I’m guessing you were expecting that? Let me know if you would like me to gather more information. Thanks HammersQuote |
| February 13, 2012 at 6:25 pm #1280 | |
| Tomek | Hi Ken, Actually, no, I was hoping that would be the answer Ok, so you can get the information (stored in JSON format) from the webserver with the /rest/item/1?output=html call. Could you email that to me (your other email got to me fine)? A couple things to try while I’m perusing that: 0) Try restarting WLPG. The reason could be that either PoG or WLPG has cached the webserver response or the error from PoG and is now failing constantly. 1) Double check that the “User Key” in PoG3 is the same as the one you used to get the REST information using Firefox (I’m sure it is, but on occasion it doesn’t copy well 2) Try putting in http://kenaldrich.com/gallery3/ in your URL box. While the program should automatically normalize “kenaldrich.com/gallery3″ to the above, maybe something is going wrong there. 3) Is it the same exact error that you’re seeing from PoG? If it isn’t, would you please email that to me as well? 4) One last thought – if you use Firefox Dev tools like before, clear the output, and then try to refresh the page (rest/item/1), you should only see one entry appear. If you don’t, could you post a screenshot of that as well? Thanks for your patience! It might be that there is some odd setup that I hadn’t accounted for. I don’t see anything obvious yet. Hopefully we’ll get to it, fix it and make it better for everyone else. Sorry that you had to be the guinea pig. Tomek TomekQuote
|
| February 13, 2012 at 8:29 pm #1282 | |
| Hammers | Tomek, I started by closing open applications and rebooting the workstation. The only thing I can think of is that something had been cached. Fixing the .htaccess file must have resolved the problem, but my test afterwards must have failed for some reason. It is getting late in the day here. Maybe I’ll rename my .hataccess file and see if that breaks it again. HammersQuote |
| February 13, 2012 at 8:41 pm #1283 | |
| Hammers | AND! I successfully uploaded a photo to my gallery with it. The gallery had some face tags for people in the photo. It successfully uploaded the face tags, however the boxes are not on the faces. There seems to be a problem with the coordinates. HammersQuote |
. But at least we’ve narrowed down the possibilities a bit!
The topic ‘Unhandled Exception when Download Album Info’ is closed to new replies.