Announcement

Collapse
No announcement yet.

Postlog Database Error, Please Help Fix!

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

  • #16
    Originally posted by Paul M View Post
    If all else fails, you might find it better to just drop the table and recreate it. Take a backup of it first if you think you may want to re-import the old logs.
    Yeah if I cannot get this solved I'll have to do that I already have a back up saved. Backed it up before I went rooting around in it
    vBulletin 3 & 4 Design & Development For Hire!

    Comment


    • #17
      What does the table structure show ?
      Baby, I was born this way

      Comment


      • #18
        You can rebuild the unique indexes in the AdminCP under Maintenance -> Repair / Optimize tables. You will need to make sure the Install directory is uploaded and that your site is in debug mode.

        You can put your site into debug mode by adding this line to your config.php under the <?php line:
        Code:
        $config['Misc']['debug'] = true;
        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


        • #19
          Originally posted by Paul M View Post
          What does the table structure show ?
          I've attached a screen shot. Click image for larger version

Name:	screen-postlog-structure.jpg
Views:	5
Size:	441.3 KB
ID:	4358417
          vBulletin 3 & 4 Design & Development For Hire!

          Comment


          • #20
            Originally posted by Wayne Luke View Post
            You can rebuild the unique indexes in the AdminCP under Maintenance -> Repair / Optimize tables. You will need to make sure the Install directory is uploaded and that your site is in debug mode.

            You can put your site into debug mode by adding this line to your config.php under the <?php line:
            Code:
            $config['Misc']['debug'] = true;
            Did all and it did not fix the table, its the same. Tried to create a new article and got the same issue as before with the PHP Warning & DB Error. Incidentally something I forgot to mention was that when I get this database error and I'm creating a new article not editing an article I can go back and refresh the home page and the article is there but it does not have comments enabled even though I did enable them when creating the article. I'm not sure if that makes a difference or not.
            vBulletin 3 & 4 Design & Development For Hire!

            Comment


            • #21
              The structure actually looks fine so you have a code conflict going on somewhere, a plugin seems the most likely cause.
              Baby, I was born this way

              Comment


              • #22
                Originally posted by Paul M View Post
                The structure actually looks fine so you have a code conflict going on somewhere, a plugin seems the most likely cause.
                Yeah but I globally disabled the plugins and it still happened that is what baffles me. Shouldn't it have temporarily solved the issue so that I could systematically go through them and find the culprit?
                vBulletin 3 & 4 Design & Development For Hire!

                Comment


                • #23
                  Originally posted by LenKaiser View Post

                  Yeah but I globally disabled the plugins and it still happened that is what baffles me. Shouldn't it have temporarily solved the issue so that I could systematically go through them and find the culprit?
                  Once the problem exists it won't go away even with plugins disabled, until the conflict is resolved.

                  So you could try disabling plugins via config.php, then recreating the table from scratch as Paul suggested. It should work then. It's then a matter of finding out which plugin is causing it.

                  To be honest I would be tempted to do as Paul suggested and just afresh with the table, it may well work then. Databases can have a mind of their own at times.
                  MARK.B | vBULLETIN SUPPORT

                  TalkNewsUK - My vBulletin 5.5.2 Demo
                  AdminAmmo - My Cloud Demo

                  Comment


                  • #24
                    Have you re-uploaded all the default files for your current version ?

                    If you are 100% sure you have disabled the plugin system, and are running the current default 4.2.3 files (and style), and it still happens, then you need to provide a clear set of steps to reproduce it, because its really unclear to me atm what exactly you are doing, so I cannot try it on my test site. That said, I find it hard to believe its not something local to your set-up as it would have expected it to have been reported long ago if it were a core issue.
                    Baby, I was born this way

                    Comment


                    • #25
                      Originally posted by Paul M View Post
                      Have you re-uploaded all the default files for your current version ?

                      If you are 100% sure you have disabled the plugin system, and are running the current default 4.2.3 files (and style), and it still happens, then you need to provide a clear set of steps to reproduce it, because its really unclear to me atm what exactly you are doing, so I cannot try it on my test site. That said, I find it hard to believe its not something local to your set-up as it would have expected it to have been reported long ago if it were a core issue.
                      No I do not think its a core issue at all, never did. I think now that I've been working on it for a bit that my database somehow got hosed since I've backed it up and imported it a couple of times. I think initially it did have to do with a particular plugin/mod because yesterday I remembered that I had a problem with comments after deleting some comments in a mod that I installed, so I bet there in lies the problem now and somehow it hosed the database in the process not allowing comments anywhere in the CMS as well as the mod.

                      What I've done is I have my demo site up and I moved my custom skin to that site and moved all the mods except the one that I suspect caused this issue and now I cannot reproduce this issue which IMO is a good thing lol. So I'll work on creating the site from scratch again and check periodically as I do so to ensure there is no problem as I go along. If I have any other issues with it I'll let you guys know. Thanks for your help.
                      vBulletin 3 & 4 Design & Development For Hire!

                      Comment

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