![]() |
Quote:
|
Quote:
|
Quote:
Rgds |
Quote:
PHP Code:
|
Quote:
HTML Code:
<!-- post #$post[postid] --> I am not sure why there is a difference, maybe I didn't upgrade that template to the latest version when I upgraded the vB software. I think that the comments which exist there, have some bad effect, try removing those comments first and see if this fixes your problem. Rgds |
Quote:
|
Quote:
I'll completely undo everything and see what happens. This has been a time consuming process, but I guess I should've removed ZT's and installed yours from the beginning. :( |
Deleting this part fixed it for me:
PHP Code:
|
I reverted the php files by commenting out little changes and deleting large changes. That got the board back. Now I'm going to attempt to install 2.3.3 from scratch. Hope this works!
|
Seemed to have worked. Only problem I've run across is that the ability to warn is missing from the member profile. Where is the problem, template or php file? I'm thinking template, but I could be wrong.
|
I keep getting this error:
Code:
Invalid SQL: |
Quote:
Sorry about that, that's what happens when one doesn't keep notes of all the changes. |
Quote:
|
Quote:
Ah and a correction, it will be in 2.3.4 in a minute, I haven't noted down the changes required in the file modcp/banning.php. I 've added a column in the userban table, where the hack stores a special message, when it bans a user. Give me 5 minutes to upload the instructions. |
Yeah i'm just saying its hard work. lol
|
Quote:
What you want me to do? Do you folks are overwhelmed with it? Do you want me to stop adding things for a while? Just let me know. For the time being, I have one more thing I want to do, in the admin_warn.php, and then I'll be ... looking for new ideas. Rgds and sorry if I cause you trouble. |
I've found two smaller errors in 2.3.4
1. In the upgrade instructions youve forgotten a small line PHP Code:
2. In the AdminCP the colspan has to be increased somewhere. (see attachment!) and btw. you have to update the version numbers in the files also :nervous: |
Quote:
// COMMENT: CHANGES BELOW AFFECT THE COLSPAN IN THE BANNED USERS REPORT // in the UpgradeToLatestVersion.txt file. Don't forget to run that query as well. Rgds and tnx |
Quote:
This seems to be the most-supported Hack here on vb.org :D Hopefully we come to a final state within the next days or do you have already more plans for future releases? haha |
I still can't find out why the warning options aren't appearing the member profile. I checked the template and member.php and they're both correct. This is the only thing I have left to test before I install on the live server (which will go much smoother since that setup is cleaner). Any assistance appreciated.
|
Quote:
k. |
Quote:
However, keep in mind, that the automaticpm was added in version 2.0 while the version was added in 2.3. And neither of them was in your table. Rgds |
Quote:
|
Quote:
|
Quote:
Please tell me if you have set that to yes, or not, so that I can see what your problem is. Rgds |
Quote:
Quote:
because i don't see this, "Allow Non-Post-related" option |
Quote:
IF that is set to yes and you can't see the links, two things can happen: 1. your template is not edited properly. 2. the user is not authorised to issue warnings. Assuming that the user is authorised, I would suggest that you check your template. One more question, if the user you are checking his CP has warning points, do you see his points? Here is what my memberinfo template looks like: HTML Code:
$stylevar[htmldoctype] |
has all the bugs in this hack been cleared out?
since its a long hack I want to ask first. |
Quote:
i have no idea what updates you've done since .4 and .5 am i missing something here? because the necessary coding that i do have are correct from the 2.3.2. please help i'm not saying hot to do your updates but there should be |
Quote:
Rgds |
nothing major but in your 2.3.5 upgrade from 2.3.3 to 2.3.4
find: Code:
$DB_site->query(" it doesn't find this because vb3 comes stock like this: Code:
$DB_site->query(" again nothing major just in case somebody else who's trying to install this doesn't think something is wrong.....or is there? :ermm: |
i updated to 2.3.5 and i still don't see the option under users profiles.
no one has been warned because i'm doing this under a test site before updatding my live site |
Quote:
|
Quote:
|
Quote:
|
Nubian,
You are right, when I was writing the patch instructions, I saw that and I thought I have made a mistake there, because the code is entering the same info in the same column twice. So I removed the last insert. I'll update the instructions, thanks. |
Quote:
1. Make sure that your member.php file has the following lines in the beginning: PHP Code:
2. Make sure you have uploaded the latest realease of the functions_warning.php file in your includes directory. Check that the file has the following lines at the beginning: PHP Code:
HTML Code:
<!-- checks for warning system --> Make sure you try it as an admin, and let me know what your results are. Rgds |
Quote:
Rgds |
Quote:
The only problem I ran across so far is when issueing a warning, it will go to a blank page after issueing it. It will actually issue the warning, but it doesn't return to any page. |
Quote:
I also changed the installation instructions for the MEMBERINFO template, so that it is easier to patch the original template. One replace operation and you are done. Rgds |
All times are GMT. The time now is 06:12 PM. |
Powered by vBulletin® Version 3.8.12 by vBS
Copyright ©2000 - 2025, vBulletin Solutions Inc.
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
![]() |
|
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|