Home / Topics / Download Manager Free / a.facebook

a.facebook

Viewing 8 posts - 1 through 8 (of 8 total)
Jun 29, 2012 at 7:05 pm #1571

mmmiro
Member

Hi,

The a.facebook element in your plugin is clashing with the theme on my website. I really like the plugin but I would really appreciate it if you would change it so that it is plugin specific.

Ciao
Miro

Jul 3, 2012 at 2:25 pm #1615

coco
Member

This is a problem that is present in this plugin even before 2.2.3; Shaon was made aware by me here… http://www.wpdownloadmanager.com/support/topic/facebook-css-issue-caused-by-download-manager/

You can find a solution for your problem there, it involves changhing some lines of code (changing the word ”facebook” to ”facebok” or ”facebox” for example) in the plugin and then uploading it manually to your server.

My opinion is that ”facebox” is what should have been there in the .css files in the first place, not ”facebook”…

I really don’t know why Shaon doesn’t make those needed changes. Maybe he wants everyone to go pro… ๐Ÿ™

Jul 5, 2012 at 6:03 am #1628

Shahjada
Keymaster

Hi,
I don’t want anyone to go to pro except he/she must need the features in pro. The css issue you mentioned is happened only for you and another 1-2 users. such a minor thing you can change by yourself. We take care of functional issues immediately, but such css issues are not in our priority list ๐Ÿ™‚

Jul 5, 2012 at 6:33 am #1630

mmmiro
Member

OK, I never accused you of trying to manipulate people into going pro. Given that it is something so simple to fix, I would really appreciate it if you would fix it. Yes, I was able to fix it myself but it cost me 3 hours to figure out why my theme was going all weird (I am not a developer) and I accused the theme developer of having bugs in his theme. Then even after I discover there is a problem I have to learn how to fix it and then when you issue a new release, I lose the fixes and I have to fix it all over again.

Also, when you say it is just 1-2 users, I don’t think I can agree with this. You may get only 1 or 2 users going to all the trouble of creating an account on your website and then filing a bug report, but I think there would probably be tens or even hundreds that don’t go to all the trouble and either uninstall the plugin (which I did, initially when I didn’t know how to fix it.) or they fix it themselves. Also, many will not go to the trouble of giving you feedback because they do a search and find that a bug report has already been filed with you and expect that given that it is such a small problem, that the next update will include a fix.

Finally, given how easy this is to fix, in the time it took you to read my reply, you probably could have fixed it about 5 times. ๐Ÿ™‚

Ciao
Miro

Aug 13, 2012 at 10:21 am #1897

coco
Member

I think a new strategy is needed, maybe reverse psychology will be better. BTW, LAST POST here, as it’s clearly futile to post and ask for help to Mr. Shaon.

So… PLEASE DO NOT FIX THIS SIMPLE ISSUE! WE REALLY LIKE WASTING OUR TIME AND CHANGING THE .CSS FILES EVERYTIME A NEW UPDATE IS OUT! THANK YOU VERY MUCH FOR IGNORING US!

Aug 28, 2012 at 9:10 am #1995

Shahjada
Keymaster

hahahaha… don’t worry… fix will be with next update

Nov 17, 2012 at 11:13 am #2807

coco
Member

Year, right. 3 months later, another version, the same .css bug. Is it really that hard to rename that damn ”facebook” to ”facebox”, as it should? ๐Ÿ™

I’m really not going to post again here – If you really don’t want to fix it just say so. I really don’t understand you – you’ve introduced a fantastic new feature in 2.2.9 (the category shortcode), but you continue to ignore the small issues. ๐Ÿ™

Nov 26, 2012 at 4:30 am #2923

Shahjada
Keymaster

ops, sorry, actually i forgot to fix it, in next update i’ll not miss it

Viewing 8 posts - 1 through 8 (of 8 total)

The topic ‘a.facebook’ is closed to new replies.