Errors from upgrading 4.1.7 to 4.1.8

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • thienhi228
    New Member
    • Aug 2010
    • 15
    • 4.1.x

    [Forum] Errors from upgrading 4.1.7 to 4.1.8

    I just upgraded successfully into version 4.1.8, i configure the config.php before upgrade and i got a mistake that i added define ('DISABLE_HOOKS', false); after <?php

    I upgraded successfully but now all the plugins are not working, but if I remove the line define('DISABLE_HOOKS', false); in config.php, I can't get into the forum (the browser will announce that the setting may be wrong)

    Therefore, I have to add the line define('DISABLE_HOOKS', false); after <?php if i want to get into forum, that also mean I have to disable all the plugins

    Please help me to solve this problem, thanks!
  • TheNewOne
    Senior Member
    • Aug 2011
    • 1033
    • 4.2.5

    #2
    did you also disable plugins and hooks as well before you updated or just add that line to your config

    Comment

    • thienhi228
      New Member
      • Aug 2010
      • 15
      • 4.1.x

      #3
      Thank you!
      Please tell me more?

      Comment

      • thienhi228
        New Member
        • Aug 2010
        • 15
        • 4.1.x

        #4
        Help me

        Comment

        • TheNewOne
          Senior Member
          • Aug 2011
          • 1033
          • 4.2.5

          #5
          answer post 2

          Comment

          • Trevor Matthews
            Senior Member
            • Oct 2010
            • 537
            • 4.1.x

            #6
            I think what is being suggested is you should go to your ACP then Options then Plugin/Hook System and see if you have Yes or No selected.
            But why that would stop you getting to the forum I don't know.

            What is the browser reporting that is wrong? What setting is it saying is incorrect??
            Regards
            Trevor

            Comment

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