Posts by displayinline

@CarlosVilora and @UXBarn: make sure you have refreshed the extension in Chrome extension panel, and then refresh the statement page.

It the issue is still here, click the Reset settings in the settings menu on bottom right, then rebuild the database. The cached data is probably broken, this will rebuild it from scratch

Perfect! I think I found the issue, you can download the new version here, it should work fine now.

Tell me if you still have issues!

Just open the browser’s developer tools (hit F12 ), switch to the console tab and copy the whole output you will find there

@CarlosViloria and @UXbarn: can you post the output of the console and post it in a pastebin? This will help me find out what may cause this

@KingDog @TutelageSystems: sure! Once the extension is stable enough, I will publish it to Chrome Web Store and to Envato Extras

Fixed the mixed paws and the first sales date detection issue! There was a typo in the code, with my username hardcoded…

You can download the new version here, then:

• Extract the file and overwrite the previous folder
• In Chrome, go to the extensions tab and click the refresh link under the Envastats description
• If your statement page is open, refresh it
• Then go in the settings menu on the bottom right, and hit Rebuild database

Tel me if this fixes the issue!

@revaxarts In fact, those are week number: hover the chart to see the tooltip, it mentions “Week XX of 2012”

@revaxarts Thanks!

Your awesome script was my main inspiration for building this!

Hmm… I think this may come from the part where the extension tries to read the statement history list on the sidebar to determine the first month available. If it fails, it fallbacks to current month only. Maybe some other extension messes with this.

I am going to see if I can retrieve this info from Envato’s API , this will be a much cleaner solution

Actually, the Envastats icon in the toolbar does nothing, it is here only for future functions

About the paws and rate issue, I am going to check what may cause this. Did you try to rebuild the database using the settings menu on bottom right? Maybe this will force the extension to parse again the statement.