Right. I don't want to have a hacked up version of this mod (so that I can try to find another fix every update) for a standard vbulletin install that happens to be in a directory called /forums. How can a standard vbulletin install in a directory named /forums not be supported by the default mod? To think that I installed the "stable" version blows my mind.
After a full week of back and forth to get to this point I decided I'd try vbseo since it looks like it seems to work well with vbet. WRONG!
I've found at least 3 bugs with a standard vbseo install and adding vbet on top. I fixed one by browsing the forum and have 2 more that are open.
You don't seem to want to help me via PM. Instead I get to typeout each new issue here again and wait a day between each reply so I can get these fixed as well. Meanwhile all my links in Google go to a blank page. Awesome!
You do realize a customer that pays for the mod and a nonbranded fee doesn't want to spend over 30+ hours and a day between issues to fix what should be standard right? The issue with if it doesn't work we'll fix it is fine but at this pace you aren't considering the value of your customers time. This mod has cost me so damn much in lost productivity on top of the $200 I paid for it that is makes me sick - and I'm still no further along than I started.
It sure seems like a lot of the "solved" problems are more from frustrated customers giving up and not replying to the issue. Why do you think that is?



