Announcement

Collapse
No announcement yet.

vBulletin Support - Large Boards.

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • #31
    Originally posted by Dilly View Post
    dklassen and jcerious share an IP by any chance?

    Of course vbulletin knows about 3rd party addons, but why should it be up to them to support them? You're talking about ten seconds of work for vbulletin support staff in one case, however in another case disabling plugins straight up may save them hours of work.

    Why make it harder than they have to? If you can't handle installing mods, don't install mods. It's very straightforward...
    I agree with Dilly.

    Comment


    • #32
      Originally posted by Fusion View Post
      Reverting a template does not, I repeat not, remove the logo. Reverting a template may change how things are presented, but it does not remove information unless it has been added in the change. The logo has always been there so it is safe.
      I said the logo and everything else. We've made considerably greater changes than just our own logo , and they definitely would be wiped out by reverting a template , depending on which template it was.

      Comment


      • #33
        I think what people are trying to say here is that first: yes, we understand vB can't support every third-party mods. But we don't feel we get a sympathetic ear from them when we have a problem. They're not even willing to let us say what our mods are - they just tell us to disable everything and revert back to the original. and JPnyc makes a good point - we can't always just revert back to the original.

        Since so often reverting to the original is NOT the answer, I feel vB should be more willing to listen to us - and to try to work with us despite whatever modifications we've made. Often times I've said "I have this mod and that mod - and I don't think that's the source of this problem, do you?" And they write back with their standard email "remove everything, revert back to the original."

        They're familiar enough with a lot of these third-party mods that they could have easily said to me "you're right, that's probably not the cause of the problem so let's look at other things and if those things don't work, then we'll go back and disable that mod."

        That's all I want from them. A little more flexibility in their support.

        Comment


        • #34
          Originally posted by JPnyc View Post
          That's roughly the equivalent of telling somebody who has a virus to reformat their hard drive. I understand your point, but the advice is completely useless. You think if you run a commercial forum that has been customized that you can upload fresh templates taking down your company logo and everything else? If that is the extent of their support they might as well not bother.
          Not by far, reuploading the default files, ADDING a new style for testing, and disabling your plugins, is like temporarly restoring to the default installation. After which, you can re-enable plugins and not use the default style, no harm was done at all.

          Comment


          • #35
            I think he's saying the harm is that for some period of time people won't see the site the way it has "always been". They'll see a stripped down version of it whether it's for a few seconds or a few minutes. That confuses and discombobulates people and that's never a good thing.

            Comment


            • #36
              Originally posted by jcerious View Post
              I think he's saying the harm is that for some period of time people won't see the site the way it has "always been". They'll see a stripped down version of it whether it's for a few seconds or a few minutes. That confuses and discombobulates people and that's never a good thing.
              We couldn't even do that. We have to shut the site down, we're a major Internet publisher, we can't put up an un-skinned forum for any amount of time. What I could do, since I'm the admin, is create a fresh style which only I can access in order to test. But that's not what we're generally told to do. If the effect is the same, then I could do that. But I couldn't disable any and all plug-ins without taking down the site, since the plug-in system is not style dependent.
              Last edited by JPnyc; Mon 30th Jun '08, 8:12pm.

              Comment


              • #37
                We ask you to make a new style with no parrent, we do not tell you to make it avaible to all of your general users.

                Comment


                • #38
                  Originally posted by Zachery View Post
                  We ask you to make a new style with no parrent, we do not tell you to make it avaible to all of your general users.
                  But what about when we're asked to disable everything? That affects the users, no?

                  Comment


                  • #39
                    For large boards that cannot remove addon features for troubleshooting, we recommend running a duplicate in a directory called testvb on the same server using a copy of the database (though it doesn't have to be exactly up to date) for testing purposes. This copy should have exactly the same addons and modifications and styles installed. It should be an exact duplicate of your live production forum's code and styling.

                    With such a test installation, it will be possible to troubleshoot, disable addons if necessary and test changes before you go live. There are over 5,000 addons and hundreds of styles available at vBulletin.org and other locations. Even if we know about particular addons, the combinations are overwhelming. We cannot be expected to know the interactions between each and every combination. Add in server configurations and custom edits by the site owners and you have almost infinite possibilities. By stripping an installation down to the basic installation in three distinct steps, we can determine where the issue is caused and by what aspect of your development.

                    Many times it could be a server configuration issue which only exists on your server however when there is extra code involved that can be very hard to pinpoint and if the developers need to get involved in fixing an obscure bug, there is a lot of time wasted if they have to look through plugin code as well.

                    So if all files are uploaded correctly and match, then we ask that you check plugins. If temporarily disabling them resolves the issue then you can be assured that a plugin is causing the conflict. You can then re-enable them and test each one individually by disabling and enabling them through the list.

                    If disabling plugins don't resolve the issue then it can be a javascript conflict, bad HTML structure, incorrrect logic in a conditional or something else in a template. A default style should revert all issues with templates. Comparing your template with a default one can help you find the issue in the custom coding.

                    If you test all new modifications, template edits and addons on a development/test installation before going live, at no time will your end-users be inconvenienced by disabling plugins or using a default style. This is the entire point of that allowance within the license agreement. We want our customers to have as little downtime as possible. Aside from hard drive space, a test installation only uses resources when it is accessed so it should not have an adverse impact on your server.

                    The only other way for us to try and help resolve your problem is to duplicate your installation on a new server and spend dozens of hours looking for the cause. This increased workload would of course be reflected in the price of the software and support fees would increase. Even with the current policies we have tickets that require 8 or more hours of dedicated work to resolve on occasion.
                    Translations provided by Google.

                    Wayne Luke
                    The Rabid Badger - a vBulletin Cloud customization and demonstration site.
                    vBulletin 5 Documentation - Updated every Friday. Report issues here.
                    vBulletin 5 API - Full / Mobile
                    I am not currently available for vB Messenger Chats.

                    Comment


                    • #40
                      That sounds reasonable actually.

                      The only thing I would ask is if they KNOW that a certain plugin probably doesn't cause the problem that they would let us skip that step for the moment and see if it's something else. Then go back to that step if necessary.

                      Comment


                      • #41
                        We can't ever be certain, thats the problem. Chances are at one point or another we've run into issues caused by all addons.

                        Comment


                        • #42
                          What I would like in such cases would be something as simple as "It could be that, check it out". I can understand this wouldn't be of use to the average vBulletin admin, but for someone that uses php, it could be a time-saver. I usually head off to vB support because I think they know the code better than I will ever. I don't want them to try to debug the issue for me, just try to point me to the correct direction, even if its a wrong guess.
                          Perhaps it would be useful to have a field in the member's area called something along the lines of "technical experience" (possible levels could be: no idea | some html | just html & css | html, css and some php & javascript | html,css and good php & javascript | guru level) and be treated accordingly.

                          Comment


                          • #43
                            perfect example here. we even opened a ticket through support, gave the vBulletin representative administrator account access, he poked around for a little while and the determination was "it is impossible to achieve this result simply with the vBulletin files, so it must be something you added".

                            Thanks, we knew that. Meanwhile we created a new style, completely unaltered, and disabled the plug-in system, and the problem still occurs. Gentleman that's not support, its auto exoneration. The primary concern seems to be proving that the software isn't responsible, rather than trying to resolve the issue. We already know the software isn't responsible. If it were garbage software we wouldn't use it.

                            VBulletin is far and away the best forum software out there. The most powerful, the most sophisticated, the most well-designed and with the best feature set, but if you should run into trouble, boxer shorts give better support.

                            Comment


                            • #44
                              Uh, what were you expecting? What else should they say?

                              Comment


                              • #45
                                Originally posted by Dilly View Post
                                Uh, what were you expecting? What else should they say?
                                I expect an honest effort to find the problem, not another attempt at acquitting the software of responsibility. I've worked support myself. I supported extremely complicated business software, which also had user scripting capability, and I had to go as far as debugging their scripts on a regular basis. If I couldn't find the problem (which most of the time I could), we got the developers in. That is support.

                                If you like, conduct a little experiment here. Go to my profile page, statistics tab, and click find all threads by. Just run through some and see how many were actually resolved, and not by me finding the answer myself.
                                Last edited by JPnyc; Sun 27th Jul '08, 1:19pm.

                                Comment

                                widgetinstance 262 (Related Topics) skipped due to lack of content & hide_module_if_empty option.
                                Working...
                                X