Visual Warning Mod , anyone got it working in 1.1.3

[James11]

I think this is a brilliat mod,  but has anyone got it working in 1.1.3 yet ?

thank you

[Teunel]

Yes, it works for me!

[greyknight17]

Do you get an error during the install? If it's just a compatible issue error, try this:

When installing a mod, if Package Manager says that the mod is not compatible with your version of SMF, try adding ;version_emulate=1.1.2 to the end of the Package Manager address in your browser. You should be in Browse Packages (Admin->Packages) while doing this. Hit Apply Mod and it should work.

[selorian]

I successfully got it installed on a clean install of 1.1.3 with limited testing of functionality.  It seems to be fine.

What I did was open the package-info.xml and added support for 1.1.3 so it could be both installed and uninstalled by the package manager instead of having to do it manually.  If you open the file in your text editor and look for lines 25 and 194 and add 1.1.3 at the end like so:

Koodi [Valitse] Laajenna

<install for="1.1 RC3, 1.1, 1.1.1, 1.1.2, 1.1.3">

Koodi [Valitse] Laajenna

<uninstall for="1.1 RC3, 1.1, 1.1.1, 1.1.2, 1.1.3">

it works like a charm.

[meadows317]

I successfully got it installed on a clean install of 1.1.3 with limited testing of functionality.  It seems to be fine.

What I did was open the package-info.xml and added support for 1.1.3 so it could be both installed and uninstalled by the package manager instead of having to do it manually.  If you open the file in your text editor and look for lines 25 and 194 and add 1.1.3 at the end like so:

Koodi [Valitse] Laajenna

<install for="1.1 RC3, 1.1, 1.1.1, 1.1.2, 1.1.3">

Koodi [Valitse] Laajenna

<uninstall for="1.1 RC3, 1.1, 1.1.1, 1.1.2, 1.1.3">

it works like a charm.

Tried that everything went through but got this on one of the selections

   Execute Modification     VisualWarning_SMF11.mod
   Modification parse error

But everything else went through again?

It gives me option of install now though

[selorian]

Which selection?  Are you using the default theme?  If so, maybe I can see what the problem is if I can duplicate the error.

[meadows317]

I tried it again and Maybe selection wasn't the right term,  just when you upload your package manager (after I changed what you said to change)   it asked for the information, yada yada..     And then I clicked on  'apply now'

And Everything says "test successful"  except for

7.     Execute Modification     ./Sources/Post.php     Test failed
14.     Execute Modification     ./Themes/default/index.template.php     Test failed


Using Default theme, yes

[selorian]

Do you have other mods installed, ones that have altered the ones the tests failed on?  If so, then you may still need to manually edit those.  My install was on a clean install of 1.1.3 with no other mods installed.

If that's the case, though, and you need help, if you give me the names of the mods, then maybe tomorrow evening I could see where the problems are occurring and help you get it working.

[meadows317]

I have the following mods installed

Member Color Link
No Temp Directory Removal (had to do this one before mods would even show with my host)
Custom Profile Field Mod
& VisualWarning

[shadow82x]

http://www.simplemachines.org/community/index.php?topic=55512.msg1154129#msg1154129

Someone got it for 1.1.3 to fix the error.

[meadows317]

http://www.simplemachines.org/community/index.php?topic=55512.msg1154129#msg1154129

Someone got it for 1.1.3 to fix the error.

I tried that one too,  and  I still got "test failed"  on
7.     Execute Modification     ./Sources/Post.php
14.     Execute Modification     ./Themes/default/index.template.php

[shadow82x]

I got my version of the mod up there now.

http://www.simplemachines.org/community/index.php?topic=55512.msg1177999#msg1177999

[selorian]

http://www.simplemachines.org/community/index.php?topic=55512.msg1154129#msg1154129

Someone got it for 1.1.3 to fix the error.

I tried that one too,  and  I still got "test failed"  on
7.     Execute Modification     ./Sources/Post.php
14.     Execute Modification     ./Themes/default/index.template.php

I tried the original version of this mod with the other mods you have installed and still didn't get the errors you're getting.  I'm not sure what the deal is.  Sorry.

[shadow82x]

It might be that the mod was upgraded wrong or theres another mod interfering with it. We will see how the new package goes.

[meadows317]

Darn,  STILL got those errors,   but took a break and installed it anyway and i think its going to work cause under "features and options" it says  Visual Warning Mod  and gives settings..

And I see under "members" it says Warning Management & Post Moderation Manager
But I cant find anywhere, where it lets me add members to the warning system (I looked in the profile area too)   and if I do find it,  can I make it so my moderators add people too?

[shadow82x]

Try replacing those files that may be corrupt from another mod. So get a fresh install and replace ./Sources/Post.php and  ./Themes/default/index.template.php it will reset your mods but thats whats causing it to not install correctly.

[meadows317]

Try replacing those files that may be corrupt from another mod. So get a fresh install and replace ./Sources/Post.php and  ./Themes/default/index.template.php it will reset your mods but thats whats causing it to not install correctly.

I replaced it with fresh copies of both,  and I still got it to show errors......
ahh frustrating

[shadow82x]

Did you make sure those files are chmoded correctly. (At 777 or 755 for some hosts) - How do I use chmod?

Also any other mods installed?

This can be the mod creators fault and it might not be coded correctly for 1.1.3 so therefore that author would have to fix it.

[meadows317]

777 for all yep..

Umm  Other mods 
the temp removal
Member Color Link
Custom Profile Fields

Its ok if nothing can be done,  I don't expect nobody to re-write it or code it better     especially   since everyone is a volunteer anyway 

[shadow82x]

Since others are getting errors in that topic I assume its a common error and theres nothing you can do. The code probably changed for that mod from 1.1.2 to 1.1.3. The only way is if someone recodes it.