vb.org Archive

vb.org Archive (https://vborg.vbsupport.ru/index.php)
-   vBulletin 3.0 Full Releases (https://vborg.vbsupport.ru/forumdisplay.php?f=33)
-   -   Advanced Warning System (AWS) (https://vborg.vbsupport.ru/showthread.php?t=71992)

Jamsoft 01-25-2005 01:40 PM

What would be the "upgrade" procedure to apply the latest patch? I just got done installing this on 5 forums, and like the idea of the buttons instead of the text.

Can I just drop a few files in, or do I need to hack some more files?

hello 01-25-2005 02:09 PM

you haven't put the attachment on yet

Rhoads 01-25-2005 02:15 PM

Quote:

Version 3.1.3 (released Saturday January 25th, 2005 GMT 15:25)

The "Warn XYZ" and "View XYZ's Warnings" links can now be substituted by two buttons. An option has been added in the Warning System Options, in your AdminCP, in order to select the style of those links (text or buttons).

As always, let me know if you have any problems.
Splendid sv1cec the buttons option, but it is Tuesday today :laugh:
Oke I installed 3.1.3 now, when de attachment is comming :squareeyed:

Delphiprogrammi 01-25-2005 02:46 PM

where's the new zip ?

sv1cec 01-25-2005 03:01 PM

That's what's happening when two babies start yelling together. You update something then leave something else out. Thank God they were asleep when I did the coding work.

OK, I just upload the zip and corrected the day LoL.

Now, the upgrade procedure is described in a file called "UpgradeToLatestVersion.txt" in the zip file. In reality, it's a couple of files you have to edit, two templates and run a query. The file edits are done in files you have already edited.

No biggie.

Rgds

docvader 01-25-2005 04:20 PM

I just installed this truly wonderful hack yesterday. Very impressive; kudos to all who have contributed to it.

And today, a new addition, LOL.

But, I'm trying to upgrade, and, the first part of the instructions:
Quote:

UPDATE `".TABLE_PREFIX."warning_options` SET version='3.1.3' WHERE oid='1'
leads to this error, for me:
Quote:

An error occurred while attempting to execute your query. The following information was returned.
error number: 1103
error desc: Incorrect table name '".TABLE_PREFIX."warning_options'
The install of 3.1.2 yesterday, was flawless, and the hack works perfectly.

I have a warning_options table, but, my vbulletin does not use prefixes, as it is an upgrade from an old 2.xx version.

Am I missing something here?

Thanks,
rich

Torqued 01-25-2005 04:29 PM

Hey, John:

When you update the 1st post, can you add the version # so that we can tell where we are w/ what we have installed vs what is posted here?

:)

Thanks!

Delphiprogrammi 01-25-2005 04:37 PM

people,

ALWAYS store a "working" version of the modified files BEFORE you try to upgrade so you can get everything back up and running with a minimum of "no working" time

sv1cec,

in your upgradetolatestversion.txt instructions are two database querys

1) this query updates the AWS version number (obviously)
2) that query will add a column in the warning_options table called textbutoption

i'm not sure since i see other querys here are that all database querys whe need to run to upgrade to the latest version ? i don't use that other system i always used your AWS i'm on 3.1.2 and no we cannot stop butter you with questions but when it's working i'll send you some coffee lol :D

edit

my links in the memberinfo info template disapperd ??

my links in the postbit template are gone to :S

rh2004 01-25-2005 05:49 PM

Hi...

I have a question

Im goingto upgrade from 3.0.3 this week and was wondering am I going to
loose the info or anything from the users that have warnings

- Upload new files
- Run datebase update
- Download all new mods
- Re-add all mods/check through

I don't have to use upgrade on the mods? just do it as new install?

sv1cec 01-25-2005 05:51 PM

Quote:

Originally Posted by docvader
I just installed this truly wonderful hack yesterday. Very impressive; kudos to all who have contributed to it.

And today, a new addition, LOL.

But, I'm trying to upgrade, and, the first part of the instructions:
leads to this error, for me:
The install of 3.1.2 yesterday, was flawless, and the hack works perfectly.

I have a warning_options table, but, my vbulletin does not use prefixes, as it is an upgrade from an old 2.xx version.

Am I missing something here?

Thanks,
rich

Remove the ".TABLE_PREFIX.", if you are not using a table prefix.

Rgds


All times are GMT. The time now is 04:15 AM.

Powered by vBulletin® Version 3.8.12 by vBS
Copyright ©2000 - 2025, vBulletin Solutions Inc.

X vBulletin 3.8.12 by vBS Debug Information
  • Page Generation 0.02305 seconds
  • Memory Usage 1,746KB
  • Queries Executed 10 (?)
More Information
Template Usage:
  • (1)ad_footer_end
  • (1)ad_footer_start
  • (1)ad_header_end
  • (1)ad_header_logo
  • (1)ad_navbar_below
  • (4)bbcode_quote_printable
  • (1)footer
  • (1)gobutton
  • (1)header
  • (1)headinclude
  • (6)option
  • (1)pagenav
  • (1)pagenav_curpage
  • (4)pagenav_pagelink
  • (3)pagenav_pagelinkrel
  • (1)post_thanks_navbar_search
  • (1)printthread
  • (10)printthreadbit
  • (1)spacer_close
  • (1)spacer_open 

Phrase Groups Available:
  • global
  • postbit
  • showthread
Included Files:
  • ./printthread.php
  • ./global.php
  • ./includes/init.php
  • ./includes/class_core.php
  • ./includes/config.php
  • ./includes/functions.php
  • ./includes/class_hook.php
  • ./includes/modsystem_functions.php
  • ./includes/class_bbcode_alt.php
  • ./includes/class_bbcode.php
  • ./includes/functions_bigthree.php 

Hooks Called:
  • init_startup
  • init_startup_session_setup_start
  • init_startup_session_setup_complete
  • cache_permissions
  • fetch_threadinfo_query
  • fetch_threadinfo
  • fetch_foruminfo
  • style_fetch
  • cache_templates
  • global_start
  • parse_templates
  • global_setup_complete
  • printthread_start
  • pagenav_page
  • pagenav_complete
  • bbcode_fetch_tags
  • bbcode_create
  • bbcode_parse_start
  • bbcode_parse_complete_precache
  • bbcode_parse_complete
  • printthread_post
  • printthread_complete