Javascript conflict about anteup HOT 15 CLOSED

I was afraid this would happen. A list of plugins that are installed on the person's site would help, that way I can figure out which one is also loading up jQuery.

I'm thinking it has to do with how jQuery is loaded across the board. I'll seek alternative methods while I wait for more information.

from anteup.

Will this work?
http://api.jquery.com/jQuery.noConflict/

I am not that experienced in jquery unfortunately.

from anteup.

Nor am I, honestly. I'm not sure if that will help at all, I'll check it out.

I'd assume it's an issue because it's either getting loaded twice (??) or there is more than one version getting loaded. Or.. I have no idea really. I do know that it messes with the slidedown area on the theme I use on Trickmod, which uses Prototype.

from anteup.

Ok. I'll try and get more info on the particular issue I mentioned, maybe that helps :)

from anteup.

Far as I can see the jquery UI is used for the progression bar on the menu, wouldn't the easiest solution be the usage of a different progression bar?

This is what I propose as an alternative (no clue if it's suitable): http://www.htmldrive.net/items/show/791/Very-Beautiful-CSS3-And-JQuery-progress-bar

Later edit: and this: http://www.w3schools.com/html5/tag_progress.asp would be even cooler -)

Oh and I left some messages on e107 forum, before moving my lazy ass to github. -)

from anteup.

In all honesty I used the jQuery UI progress bar because it was easy to implement. In reality the old progress bar worked just fine, but I thought I could trim down on some crap if I started to switch some things to jQuery, especially since the core will be using it by default in 2.0.

As far as your suggestions, I totally like the HTML5 version. Actually they are both nice, but the HTML5 version would require less overhead, which can never be bad. I'll look into these alternatives.

Can anyone confirm or deny that the "add new entry" breaks anything? I'm strictly speaking from a standpoint of using either the Core admin theme or the Jayya theme. I understand that the menu item being active would probably break the functionality if someone was using a non-admin-designed theme.

Finally, I personally prefer the use of the issue tracker here. Mostly because I can keep discussion about issues separated easier this way.

from anteup.

HTML5 tag will work, but styling it will not work as expected.
I'm doing some research to see if it's possible to style it using CSS at all.

from anteup.

Well so far all the past donations were entered manually, the only donation received since plugin installation was never registered by the plugin so I added it manually. Regarding the manual entries displaying same date 01/01/1970, that is just in admin interface, on donations.php the dates are loaded accordingly. I am still puzzled why the donation was treated like a transaction (with confirmation and shipping the product links)....but that's for another issue signaled on this tracker I guess. -)

from anteup.

About the styling of html5 progress tag: http://www.useragentman.com/blog/2012/01/03/cross-browser-html5-progress-bars-in-depth/

from anteup.

Yeah, I'm reading that article now. I'm about 90% finished with implementing the HTML5 progress bar.

from anteup.

Alright, I commit the HTML5 progress bar code. Please grab the files (anteup_menu.php and e_meta.php) and see if you have any conflicts.

from anteup.

No issues anymore, it works perfect in Firefox and Chrome, it doesn't display any bar (of course) in Internet Explorer 9 (probably html 5 related/old timer browser). A clean solution and from a user perspective you can't even tell the difference on the progress bar between the old jquery UI one and the new one. I also deleted/added manually some cash entries to see if the display bar is dynamic (it is). HTML 5 will change so many things for the better.

from anteup.

IE is always behind. :(

Like you said though, the tag was designed to allow for text to be displayed if the browser being used didn't support that tag. I left it blank so the end-user won't even know that there is an issue with no progress bar.

from anteup.

Yep I guess this one is solved. jquery and jquery UI is great but for this particular usability it was just not worth the effort and the further incompatibility issues generated with other 3rd party plugins.

from anteup.

I'm going to close this then. If people still have problems I'll reopen it and investigate further.

from anteup.