All Addons are DONE (except for templates)

I just finished the coding for the Answers addon, this means all the addons code is DONE. The one exception is that the links templates are NOT done. I am now starting to package them up and will post the ZIP file in a little while.

47 réponses sur “All Addons are DONE (except for templates)”

  1. ok, first bug, i THINK it’s a major one:

    Warning: require_once([path]/mtf/class_mtf.php) missing file… 🙂

    hey, did you clean the files? the file « mtf_master_functions.php » is still there even if not needed anywhere…

  2. here is the update. i tested only the installation and found a lot of bugs, like missing TABLE_PREFIX all around… always work with a prefix, it help debugging.

    also, there are missing fields in the mtf_forumfield table, i don’t know if i added the right ones, i suppose we need to find all about this.

    also, compare the files, there is some edits all around.

  3. no problem for the bug, ya know, i’m the beast here, if i see no bugs, i would not hire you.. lol

    also, that’s why i always say to work on a clean vB, with nothing else than a test ground… add prefix, default everything…

    oh, i forgot …. THANKS!… you’ve done some great job yet, and it’s promissing.

  4. oh. btw, another feature: « answered/supported » …

    it’s simple i think, but can be exploided largerly in the future. in forum X, when staff answer a thread officially « with the voice of the staff », that post can become the support answer, and be tagged as well… so the members find the staff answers easily instead of reading hundred of answers from anybody, without finding the official answer…

    i first find that idea from the Howard Stern’s official forum (customized by me)… it was asked that each time Howard answer in a thread, his posts have a different postbit, flashy, so everybody knows he answered it… and in the forumdisplay the threads where he answered are flagged…

  5. ok, i still face the error on all showthread pages:

    Warning: array_merge() URL= » »]function.array-merge[/URL: Argument #1 is not an array in [path]/showthread.php(984) : eval()’d code on line 2

    Warning: array_merge() URL= » »]function.array-merge[/URL: Argument #2 is not an array in [path]/showthread.php(984) : eval()’d code on line 2

    i do not understand that array_merge, so i can not fix it… i think it’s the only bug that block me from using this version…

  6. you did not correct my error report in post #24:

    $mtf_fields = ($foruminfo == ‘default’ OR $foruminfo ==  ») ? array_merge($vbulletin->mtf_postfield, $vbulletin->mtf_postfield) : $vbulletin->mtf_postfield[« $foruminfo[mtf_type] »];

    the array_merge … 1, i don’t know what it is used for, we can not merge two variables that are not arrays, and 2, we need to check if they exists before the merge… 🙂

  7. ok, bug fixed…nope… anyway, found why…

    hook: fetch_threadinfo_query … we absolutely need a mtf_postfield to make this error go, so we need to verify everything. i had that error until i create a post field.

    i suppose it’s the same for the other arrays… so we need to make sure all these foreach are correct.

    note to myself: kick Drew’s ass about a clean install…

  8. @Drew 21024 wrote:

    I don’t know why the error never comes up on my test bored :confused:

    because your board was bored, you say it yourself.. lol

    error wrote:
    Warning: Invalid argument supplied for foreach() in [path]/includes/functions.php(1237) : eval()’d code on line 7

    Warning: Cannot modify header information – headers already sent by (output started at [path]/includes/class_core.php:3277) in [path]/includes/functions.php on line 3087

    when we have no post field, the error come up…

  9. i think i know what it is.. I think it has some thing to do with old postfield cache.. Because i think i had that error until i cleaned the cache i will add a new page to the MTF admin called « Clean Up » where you can rebuild all the caches and that should really fix most errors..
    And the reason adding a new field worked was because that re built the cache.

  10. ok, i’m not really happy with all that i had to fix this morning. i had to recode a lot of things and fix a lot of typos during install of any addon, and i’m not even able to make them work because the postfields have no phrases related to them, there is duplicate functions that are not even related to anything in our code, and the system was not made to delete the postfield_data fields so i had to fix that also…

    sorry to see what was NOT done in the last 3 weeks since you said all and everything was done and working. you never tested the installation, you never checked on a clean vBulletin and you did not even take the time to clean your code, so i have to make it myself… so i lost a month of work waiting for you to bring me a solid result, as you said it would me.

  11. yeap. i’ll be testing the installation by the day and try to finish the templates (which is easy, but hard to understand when you know nothing of CSS)…:)

    that’s one thing i know for sure…

    so that’s it for the day.