Version: 3.0.1, by The Geek
Developer Last Online: Jan 2019
Category: BB Code Enhancements -
Version: 4.0.0
Rating:
Released: 12-20-2009
Last Update: 01-16-2010
Installs: 1363
DB Changes Uses Plugins
Additional Files
No support by the author.
From the makers of Smooth and Jazz comes the singing sensation my mom has been waiting months for:
AME3. Bigger. Badder. Bestest.
NOTE ABOUT vB4.0.3: ------------------------------------------------------------
vBulletin 4.0.3 has changed the way video codes are handled and in the process, inadvertently broke AME3. I have submitted a bug report and believe that the issue will be quickly resolved. There is a manual fix you can apply for 4.0.3 here in the interim.
-----------------------------------------------------------------------------------------------
AME3 is the sequel to the multi award winning AME 1x and AME 2x systems. AME3. This time, its different.
It allows users to simply paste URLs into their message without having to use the video bbcode or video popup box.
It allows you to add, edit and customise the video definitions that ship with vB4
It allows you to import community created definitions to extend the system in ways you otherwise couldn't.
Now you can use AME anywhere you can use video bbcode: posts, blogs, visitor messages, the CMS, etc...
Note that I am releasing this early for beta testing and general feedback. There is currently a bug in RC2, RC4 and 4.0.0 that will prevent AME from working however there is a workaround posted below.
I have written a pretty comprehensive readme and attached it seperatly to this post. I suspect both this post and the readme will get updated as AME3 becomes finalised.
I may not be able to install 4.0 for a while, but that doesn't mean I can't develop definitions. I just won't be able to test them personally. What do I need to know that makes defs different in AME 3?
Because in vb4, AME uses vbs new [video] tag, the old [ame] tags will become redundant. Because of this and many internal changes, the upgrade path will actually look like:
1- uninstall AME2.x but leave the [ame] tags intact
2- install AME3
3- Run conversion tool which will convert ame tags into video tags.
Well, I'll ask my question here, it's a new version, it may be more appropriate in this thread...
In what step do we upgrade vB4? Before step 1, or before step 2?
I may not be able to install 4.0 for a while, but that doesn't mean I can't develop definitions. I just won't be able to test them personally. What do I need to know that makes defs different in AME 3?
You won't have any problems updating most of your definitions - however because its vB doing the actual processing, there are some limitations to what can no be converted. Basically 1 parameter. Ill whip up some info and put it in the readme once I get it updated for gold.
Quote:
Originally Posted by Alan_SP
Well, I'll ask my question here, it's a new version, it may be more appropriate in this thread...
In what step do we upgrade vB4? Before step 1, or before step 2?
You can upgrade vB4 first or uninstall AME2x first. Remember though that if you upgrade vb4 first AME2x isn't compatible with vB4 so you will have to disable it AME untill it is uninstalled.
Fatal error: Call to undefined function ame_fetch_providers() in /home/xxxxx/xxxxx.com/admincp/ame.php on line 216
and this when i rebuild post
Code:
post 45:
Warning: include([path]/ame/ame_prep.php) [function.include]: failed to open stream: No such file or directory in [path]/includes/ame_prep.php on line 366
Warning: include() [function.include]: Failed opening '[path]/ame/ame_prep.php' for inclusion (include_path='.:') in [path]/includes/ame_prep.php on line 366
This version fixes a few issues with vB4 gold that was released yesterday and a few additional bugs users have noticed during the beta test.
I have verified that the bad hook bug mentioned in the first post still exists :down: I have included a safety check in ame's admincp to make sure users have removed it.
After uninstalling this modification, the default video-Tag doesn't work any longer...
Any idea how to solve this?
I can't confirm this. There isn't anything in AME that would stop the default video code from working. The only exception could be if you used URLs that vB's video code wouldnt parse to begin with. Can you provide an example?