Jump to content

  2. → Viewing Profile: Posts: huskihuskihuski
  •  

    • huskihuskihuski's Photo

    • Overview
    • Profile Feed
    • Likes
    • Friends
    • Topics
    • Gallery
    • Files
    • Blog
    • Tutorials
    • Stats

    huskihuskihuski

    Member Since 12 Nov 2007
    Offline Last Active Apr 30 2012 12:42 PM
    -----

    Posts I've Made

    In Topic: Upgrading impossible with leftover blog module

    18 April 2012 - 02:11 AM

    I hate relying on IPB to fix problems as yes they can usually fix anything, you won't find out the solution so I prefer to figure it out so I can learn more about the software.

    Was able to install the DB Customization Manager program

    Quote

    DB Customization Manager  v1.0.5
    Scans your database for objects not part of a standard install, to help you remove 'junk' from your database

    I think Michael wrote this program a while back and this was a version for 3.1.4
    After stripping many things I was able to get past this blog road block and get 3.3.1 installed.

    Very last thing is IP.Content or CCS whatever it was called back then version 1.0.1 will not let me upgrade to the latest version and even 'forwards' all admin cp logins to the upgrade page, with no way to access the admin cp unless you manually put in a different path besides the dashboard.

    Anyway, this time even using this special utility, the IP.Content upgrade still comes up with an error complaining about something wrong within one of the tables, when disabling the app, thats ok, but when trying to delete/uninstall it, a database error comes up, however it does deleted the ccs tables.

    I then went into the ibf_upgrade_history table and took out two rows, ccs 1.0.0 and 1.0.1 however that didn't trick the upgrade, something else sees things left over which i suspect would be files that were uploaded ?

    I may have an old version of ip.content 1.0.1 on an old hard disk, but i don't think just overwritting the attempted upgrade files of 2.3.1 with old 1.0.1 files will get past the database error which is currently looking for the old content tables.

    Does anyone know exactly where or how IP.Board stores upgrade history info, I want to wipe this old version clean off and let it treat as a new app install.

    Thanks

    In Topic: Upgrading impossible with leftover blog module

    08 April 2012 - 01:59 AM

    Going back to a previous 3.1.4 database I am able to see IP.Blog now listed in the 'Applications not installed' area but when trying to upgrade to IP.Board 3.2 or 3.3 the error listed in the post above appears so I'm still stuck.

    Any ideas on where IP.Board is holding on to these blog leftovers and how to upgrade to IPB 3.3, thanks.

    In Topic: RESOLVED: IP.Board 3.2.3 to 3.3 beta 2

    07 March 2012 - 01:30 AM

    You were right it was the adcode, even though the sidebar hook was disabled the adcode integration on/off setting was still on with my google adsense code for topics in there causing the error

    According to a recent post in the 1st topic listed above, this issue will be fixed in beta 3

    thanks Andy

    In Topic: RESOLVED: IP.Board 3.2.3 to 3.3 beta 2

    04 March 2012 - 03:59 PM

    had the adcode hook but have actually disabled all hooks including the shoutbox. Seems to be happening to others, will keep an eye on the following threads here:

    http://community.inv...cstopicsetdata/

    http://community.inv...ew-topic-guest/

    thanks Andy

    In Topic: Spammers are the scum of the earth

    25 February 2012 - 03:32 AM

    i suspect the spam script now identifies a 'tainted' proxy ip or email address' that this hook checks from the stopspammer database, auto removes it from the spam script and continues on. The hook is great and it worked fantastic, just believe this the spammers are finding a way around it with fresh IPs and emails and quickly flooding boards and that certaininly isn't this hooks fault, just frustrating

    1. Invision Modding
    2. → Viewing Profile: Posts: huskihuskihuski
    3. Privacy Policy
    4. Guidelines ·