Version: 2.1.2, by Elite_360_
Developer Last Online: Mar 2022
Category: Add-On Releases -
Version: 4.2.x
Rating:
Released: 11-08-2012
Last Update: 06-09-2015
Installs: 170
DB Changes Uses Plugins Auto-Templates
Code Changes Additional Files
No support by the author.
Mark As Installed = Support For Version Information And Features for Next Version: Go to Post #3
This Mod Works From 4.2.x
Description:
Markup Everywhere well almost like 90% if you use every feature that vb has.
Added Member Action Drop-Down where it did not have it.
Username Font
Username Prefix (Clan Tags) and the Option to Change to a Suffix in "Usergroup Manager"
Auto Template Edits
If you don't like the way this mod does the HTML markup,
It's compatible with vBNinja mod Ultimate Usergroup HTML Markup Customizer
but username prefix (Clan Tags) and username font will not work with this mod.
Re-upload your vb version all the file but delete the install directory and the includes/config.php.new file. Don't Run Vb Upgrade
Then go to Installation
--------------------------------------------------------------------------------- Installation:
1. Upload the contents of upload folder to your forum root.
2. Import the product-e360_markup.xml product file go to AdminCP >
Plugins & Products > Manage Products > [Add/Import Product]
3. Go to AdminCP > Settings > Options > e360 - Usernames HTML Markup Options and config.(There a link to the file edits there too)
Only if you want to use User Name Prefix and Font
4. Go to AdminCP > Usergroups > Usergroup Manager > and config each usergroup "e360 - Username Html Markup Permissions"
Ok,updated to 4.2.2 from 4.2.1. In the stats at the bottom of the index page I show TWO blog stats for entry and user - one is default and one is the e360 mod. How do I fix this?
Also, should I be concerned about the upgrade overwriting any other files, which means I will have to change the code via the readme file for these files again? If so, which files were affected? Thanks!
1. If you want markup for blog stats then disable plugin "Forum Home: Process Blog Stats" if you don't want markup then disable "e360 - Username Html MarkUp: Forum Home Process Blog Stats"
2. All Files will be affected so yes you will have to do the steps over in the readme text file for template only if you reverted them
1. I do want the markup stats. What happened after the upgrade is I show DOUBLE BLOG stats at the bottom. One appears to be the default that comes with VB (no user markup), the other is the markup from this mod. I want to get rid of the vb version and use your mod version. So, with that said, I am a little confused by your reply. Is this something I would change in code, or by doing the upgrade did it enable the default (vb version) of blog stats, where I need to disable the VB version, which would leave yours? Thanks.
1. I do want the markup stats. What happened after the upgrade is I show DOUBLE BLOG stats at the bottom. One appears to be the default that comes with VB (no user markup), the other is the markup from this mod. I want to get rid of the vb version and use your mod version. So, with that said, I am a little confused by your reply. Is this something I would change in code, or by doing the upgrade did it enable the default (vb version) of blog stats, where I need to disable the VB version, which would leave yours? Thanks.
Yes when you upgrade vb it will enable the default version
1. go to admincp > Plugins & Products > Plugin Manager > search for "Forum Home: Process Blog Stats" and disable the plugin
When the new mod version comes out, will I have to manually remove all the code update into the templates that was specified in the readme.txt?
Do you have a rough estimate for the new mod roll out? I recently did the 4.2.2 upgrade and I think some things got over written, and was hestitant to manually change the files back, as per the readme.txt file, if it involves manually changing this code to something different when the new version comes out...
When the new mod version comes out, will I have to manually remove all the code update into the templates that was specified in the readme.txt?
Do you have a rough estimate for the new mod roll out? I recently did the 4.2.2 upgrade and I think some things got over written, and was hestitant to manually change the files back, as per the readme.txt file, if it involves manually changing this code to something different when the new version comes out...
For next version you will have to revert all the templates re-write all the files that where edited since the code has change for time frame of next version release i don't know been busy.