Sunka
Customer
Fillip H. said:I'm a bit confused, if another image resizer mod works, then I'm not sure I see how it still can be a bug in APTL that I can fix for you?Sunka said:
Unfortunately our support services don't entail re-writing significant portions of other modifications to make them compatible with ours
Yes, it works, but Highslide resizer is not what I want it to be installed. Four years ago i had on phpBB forum installed Highslide for resizing images and I have uninstall because it is not what I want.
Fillip H. said:Sunka said:
This can happen if a mod has not integrated itself with the "show post" script (showpost.php).
Many of our mods such as vBActivity & Awards had to get this compatibility update applied, but since the usage of that file is largely defunct in vB4, not many mod authors bothers adding support for it.
vBCMS and vBBlog has support for it, though
At this time there's no way to work around these issues without significantly re-writing the way APTL works, which is not something we can do straight away
You can ask BOP to integrate with showpost.php and it will work, however
All this story would not start if all this errors start when I install APTL 2.0.0, but they do not. All started with last update, and because of that fact, I said that bug must be in APTL mod.
Let change sides for 5 minutes. You buy my Mod, you install and everything is OK, we both are happy. Then you download update for my MOD, You than uprade mod and some of your other crucial mods not working. Who you going to ask for help? In your opinion in that situation, who's Mod have bug?
Fillip H. said:
Nop, because all working (not all because still there is some bugs on earlier versions of APTL that you give up in finding solution. Hint, use search for my threads create her). But maybe something was changed by some of you because (I do not remember who) of you guys have worked for some bug on my server earlier, and maybe somethin in plugin change than, and because all working OK until this upgrade. I do not know, I just think.
Yes you have, I do not deny that but only after my insistence, begging, shouting in the dark (lol) this problem/bug is not forgoten.Fillip H. said:
Fillip H. said:Sunka said:
Right off the bat I pointed out exactly why the issue was happening and why I could not fix it (the issue was, as you yourself found out, with the Image Resizer mod you were using) and the issue could have been resolved right there.
After you claimed the issue was present in the previous version of the mod, I launched a file comparison between the v2.0.2 download, and v2.0.3 download (just in case I had missed any changes) and let you know that the code had not changed.
I admit that I shouldn't have waited for you to request me to go to your site, and for that I apologise. However, please bear in mind that in my head, the issue you were describing ("v2.0.2 and v2.0.3 made changes that broke this") was literally impossible from my PoV (the actual code itself showed that no such change had been made), and I found it strange that you did not accept my judgement on this matter.
I gain nothing from lying to you and saying that no changes were made if changes were made. In fact, I would only be causing myself more problems, not only because you yourself could launch a file comparison - thus publicly expose me for a liar, but also because someone else would be reporting the same problem and we'd be back to square one.
Know that whenever you or anyone else report a bug, I am probably even more excited than you are at getting it fixed A.S.A.P. - the sooner it's fixed, the less support threads are created about it, and the less customers (or even free Lite users) feel like they're using a broken product.
Again, I respectfully disagree that I did not help you from the outset.
Unfortunately, the reality is that sometimes, vBulletin and other mods are at fault. What would you want me to say, if I uncovered a bug in vBulletin or in another mod that made my products not work as intended?
An example of this is vBulletin 4.0.2. That version, and that version alone, won't work correctly with a lot of DBTech products. Why? Because they accidentally changed 1 small block of code that created profile tabs. The result was, no profile tabs showed up for any modification (including their own vB Blog product).
4.0.1 and 4.0.3+ are not affected by this issue. If a customer running 4.0.2 comes to me and says "Your product is broken, the profile tab does not show up!" what would be the correct answer, in your eyes?
My answer would be to ask them wait for 4.0.3 to be released (assuming this report was created when 4.0.2 was the latest version) or to downgrade to 4.0.1, because I cannot fix bugs in vBulletin.
Perhaps not the best example because since the block of code changed was so small, I could easily do a comparison between 4.0.1 and 4.0.2 and identify the broken code, then provide a fix.
My point is, we do not offer support for other mods or vBulletin, so if there's a conflict with another mod that we are not able to resolve from our end (of which there have been a few, to the point where we had to reduce functionality in our vBShout product to work around the conflict) then we will have to tell customers that the problem is with the other mod or with vBulletin and we cannot help.
Sorry if that was a huge ramble that made no sense, I'm not very good at explaining things to others, putting myself in their shoes
If you still disagree with me or want a better explanation, simply mention Cosmic - he'll do a much better job of explaining this than I did
Yes, yes...
Of course that before asking for help here, I try to find solution by my self. I compare old and new files too, and find that something is changed, but I have not so knowledge in coding, so for some part of code I did not know is that only for fixing new menu in vbulletin or is something else.
You say that I did not accept your judgement on this matter. Yes I have, but you did not accept my explanation of problem. Those bugs started after update to v2.0.3. before that, they did not exist.
And again i did not said that you did not helped me. Yes, you helped, but only if customer insist, beg, be boring... bla bal
Thats my feeling, my conclusion for 3-4 times I asked help here. You give help, but customer have to scream for it. And that is wrong.
I know that in many situations creator of Mod do not give help if another mod is conflicting, only when there is bug with default vBulletin files/codes, but there is not such stuations if you look "tree of life" for this bug.
Probably I would never ask or at least not screaming so much here, if bug was start if I update mod for resizing images in posts, not APTL mod.
Fillip H. said:
My opinion is the opposite of your, and we both have right for it.
I do not want to argue with you guys. I just want to help me when I need help and try to have here good relationship like Seller => Buyer must have.
I still have some bugs.
Maybe this is impulse for your new mod (resize images in posts)
Sory for my not so good english language.
Sunka from Croatia
