Enhanced Editor gone after 4.1.7 > 4.1.8 Upgrade

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Zaggeh
    Member
    • Oct 2011
    • 67
    • 4.1.x

    [Forum] Enhanced Editor gone after 4.1.7 > 4.1.8 Upgrade

    I just applied the 4.1.8 upgrade and the enhanced editor isn't showing up anymore. What kind of things should I check to troubleshoot this? "Suspect File Versions" isn't complaining about any missing or modified files or anything.

    Edit: I should add that I read this: https://www.vbulletin.com/forum/show...-after-upgrade and both my mobile style settings are set to "None" and my default style is "Default", which is truly the default. The only thing that has been modified is some styelvars for the titleimage and some background colors.
    Using vBulletin 4.x Publishing Suite at Clylla Game & Guild Portal
  • Troy Roberts
    Senior Member
    • May 2000
    • 339

    #2
    Another potential cause in 4.1.8 is Cloudflare minify. The solution is to disable it.

    Comment

    • Wayne Luke
      vBulletin Technical Support Lead
      • Aug 2000
      • 74172

      #3
      Do you have your CMS installed in a different directory than the rest of vBulletin?
      Translations provided by Google.

      Wayne Luke
      The Rabid Badger - a vBulletin Cloud demonstration site.
      vBulletin 5 API

      Comment

      • Zaggeh
        Member
        • Oct 2011
        • 67
        • 4.1.x

        #4
        I have the forum installed in a diff.... ohh, wait. that's probably it, let me try copying over the forum folder from the new installation package.

        Also, I have no clue what cloudfare is, so I'm guessing I don't have it. :-P
        Using vBulletin 4.x Publishing Suite at Clylla Game & Guild Portal

        Comment

        • Zaggeh
          Member
          • Oct 2011
          • 67
          • 4.1.x

          #5
          Okay, I re-uplaoded the forum fodler just deleted the old one), still no sign of the enhanced editor (it is enabled under my general settings)
          Using vBulletin 4.x Publishing Suite at Clylla Game & Guild Portal

          Comment

          • whitey10tc
            Senior Member
            • Jan 2011
            • 415
            • 4.0.x

            #6
            revert the editor css files. Worked for us.
            www.cdmagurus.com
            www.cellphone-gurus.com

            Comment

            • Zaggeh
              Member
              • Oct 2011
              • 67
              • 4.1.x

              #7
              What do you mean? Revert back to 4.1.7? I shouldn't have to do that...

              The only CSS modification I have is additional.css with the following changes:

              .body_wrapper { margin: 0px 35px 0px 35px;
              }


              .footer_copyright a:link{
              color: #ffffff !important;
              }


              .footer_copyright a:visited{
              color: #ffffff !important;
              }
              Everything else is done through stylevars.
              Last edited by Zaggeh; Thu 15 Dec '11, 6:34pm.
              Using vBulletin 4.x Publishing Suite at Clylla Game & Guild Portal

              Comment

              • Zaggeh
                Member
                • Oct 2011
                • 67
                • 4.1.x

                #8
                Okay, it WAS the forum folder. I uploaded it to the wrong place when trying to fix it last night, whoops.

                All better now.
                Using vBulletin 4.x Publishing Suite at Clylla Game & Guild Portal

                Comment

                • sticheno
                  Member
                  • Jul 2008
                  • 38
                  • 4.2.x

                  #9
                  Check out this answer here posted by one of the support folks. I think this is what some are looking for and it fixed it for us just now. I had my default style entered in as the mobile style and that caused the problem.

                  Comment

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