Lee Mason

we have fixed this on a client site so it works in ie8. its pretty simple, but there are a few changes needed:

1. rgba css doesn’t work in ie8 so we set some default background colours on the overlay div and .emodal class (black and white). for a full sultion you would need to detect browser in he script and add a hex rather than rgba in the js

2. you use the word “class” as variables in the defaults object. this is a reserved term, hence the expected identifier error in ie8 (other browsers just ignore it). we just changed that reference to “class_name” in the js file.

3. because of number 2 there is one part of the code (sorry forgot which part) that just passes all attributes to the object to be set. this had to be changed as otherwise it would a attribute of class_name=”classes” to the element.

with all that sorted it works in ie8, but obviously the css we have used is hard coded. for the plugin i would suggest browser detection and prevent the hex being converted to rgba for that browser.

yes monolog is a logging system which allows you to send logs to pretty much anywhere.

WordPress doesn’t really have any built in logging capabilities which potentially means people are using the site and getting errors and no body knows it. could be built into wp_die and WP_Error

i know what you mean with 5.2 but nobody is going to move forward without being pushed, php is on 5.5 already.

I will get round to it, but it’s not going to be for at least 1 month. I’ve got too much paid work on at min.

I will update the plugin when I can, but paid work feeds me so I need to do that first.

I will update thread when its ready.

sorry guys, sorted the end date and not the start.

just commited a new release with a fix in place

i fixed it in the latest release, please make sure your up to date.

this should be fixed now

will be trying to add this soon

will look into it

will add it to the list, thanks for the request

new version with fix is being added to the svn as we speak.

ahh, just replicated the issue, im fixing it now.

yes the invoices are private and can only be viewed by logged in members that are attached to that invoice.

the user must log in to view the invoice for security.

pot file will be added in the next release, thanks for your interest in the plugin, how are you finding it?