Bruji

A slight update to my Jan 12th post about the edit window popping up. With beta 110, this issue still happens, but after hitting ESC, focus does return to the Multi ++ add window, so I no longer need to hit the tab key. But the main issue of manually entering an ISBN and the add title/edit window po...

Conor - I haven't found any unusual datestring issues since your 110 beta. The focus issue is still there, as I did something unusual a bit ago and copy/pasted an ISBN into the multi add window: 1935507338 then I hit return [on the main part of the keyboard]. Bookpedia then added and opened the book...

This was a tough bug to fix. As it has a lot to do with localization and date formats preferences on the computer as FineWine pointed out. Also that it's no longer supported by Apple to be lenient on how you enter dates. They want you to stick to the formats you have on your preferences. Do please ...

Yeah, I posted before I tested. Sigh. The system preference was also like yours and I assumed that is what was causing the issue. But I just tested it [busy day!] and if I type 11/15/2018 into the Purchased On field in Bookpedia, it results in the year 2020 being added. My 'Other dates' also looked ...

Using Bookpedia 5.9.2, beta 109 on macOS 10.13.6 on a mac mini: Filling in the "Purchased on" data as "11/12/2016" results in the year being changed to 2020. The only way to get the year to be accurate is to type "16" instead of "2016". 2 - Now check you have...

I've disabled the 'return to search window after adding an entry' and the issue still persists. Also the date bug mentioned in the original post still persists. Using Bet 109 of Bookpedia now under 10.13.6.

Could you try disabling "Return to search window after adding an entry". Should not be related and it's not the case that is hoping up but the edit window. But since I have not been able to repeat it, looking for settings that might be affecting the workflow when manually typing out the I...

With the latest beta -108 - the Price field is not showing the correct data. It shows CSS code instead: .a-tab-content > .a-box-inner { padding-top: 5px; padding-bottom: 5px; } EDIT This seems to happen with most items, but not all. A couple of examples [my data is set to only come from Amazon US, w...

Using Bookpedia 5.9.2, beta 108 on macOS 10.13.6 on a mac mini: Filling in the "Purchased on" data as "11/12/2016" results in the year being changed to 2020. The only way to get the year to be accurate is to type "16" instead of "2016". Manually adding items b...

I just noticed this thread - I'm working well under beta 103 with Amazon Test. I have not re-tried with my own credentials since it appears that I do not yet have a permanent Associates account yet since I have not yet met the 3 purchases via my links in 3 months. When that happens [i now have 1 cre...

Thanks for the details. To check on your credentials after searching do look in your console log as it would list any errors from the Amazon API directly reports. You can access the console log via the application 'Console', located inside your Applications/Utilities. The newer messages are towards...

FineWine wrote: Both work on my version beta 101 using Amazon Test

Interesting! Using my own credentials they don't work. I guess I will switch back to Amazon Test.

Just to confirm - I am unable to find any ASIN with beta 101 of Bookpedia. Another one - a map a friend of mine publishes that I sell: B001CV2Q5I I am using my own Associate ID and access/secret key [and to follow up on the prior message about the IAM rights - leaving them blank, I wasn't able to us...

I've been on vacation for a week, but just FYI, beta 101 of Bookpedia produces no results when using the cogwheel and searching Amazon US only for this ASIN: 1406348279 I've not had books to enter in mass lately and won't for a while as I play catch up with a large backlog of FBA items I need to shi...

Hi Conor, So I finally have had the time to do some data entry and unfortunately Bookpedia isn't working with the Amazon Test check marked, for most of the barcodes that I scan in. The barcodes usually are ISBN13, not ISBN10. I am unsure if that makes a difference, though one ISBN13 barcode did scan...