noisen - Aeva Media et associés - Sujets
There's a 'quick' solution, just disable 'lookups' in the Aeva settings. This should help, although you'll still have to manually modify protocols to '; instead of '; when posting a video.If you want a full-fledged fix, you'll have to do with my diff patches. I'll post updated versions of the AeMe 2.10 files, too, but please remember not to share these outside of this board. Feel free to share the diff patches, though.If you didn't change the original AeMe files, then feel free to just dropped the fixed files into your Sources folder.Or, of course, switch to Wedge. Important note: I only spent an hour or so on this fix. It's quite ugly, as it was backported from the Wedge codebase, and I didn't bother to make many tests for the Aeva-Embed.php changes.Code: [Select]]>]--- Sources\Subs-Aeva-Sites.php 2010-10-08 11:56:08.000000000 +-0200+++ Sources\Subs-Aeva-Sites.php 2015-05-13 16:07:02.000000000 +-0200@@ -139,27 +139,27 @@ array( 'id' => 'ytb', 'title' => 'YouTube', 'website' => ';, 'type' => 'pop', 'added' => '<4.0',- 'pattern' => 'http://(?:video\.google\.(?:com|com?\.[a-z]]>]]]]]]- 'movie' => ';,+ 'pattern' => 'https?://(?:video\.google\.(?:com|com?\.[a-z]]>]]]]]]+ 'movie' => '[url]]>]] 'size' => array( 'normal' => array(480, 385), 'ws' => array(640, 385), ), 'ui-height' => 25, // or v=MxGofCFHYCc (all hail Jochen Hippel!) // On Google - // - Example of "Embedding Disabled By Request"- 'fix-html-pattern' => '<object [^>]]>]]]- 'fix-html-url' => ';,- 'lookup-url' => 'http://(?:video\.google\.(?:com|com?\.[a-z]]>]]]]]]]]- 'lookup-actual-url' => ';,- 'lookup-final-url' => ';,+ 'fix-html-pattern' => '<object [^>]]>]]]+ 'fix-html-url' => '[url]]>]]+ 'lookup-url' => 'https?://(?:video\.google\.(?:com|com?\.[a-z]]>]]]]]]]]+ 'lookup-actual-url' => '[url]]>]]+ 'lookup-final-url' => '[url]]>]] 'lookup-title' => true, 'lookup-title-skip' => true, 'lookup-pattern' => array( 'id' => '<id>.*?:([\w-]]>] 'error' => '<internalReason>(.*?)</internalReason>', 'noexternalembed' => '<yt:accessControl\saction=\'embed\'\spermission=\'denied\'/>',@@ -160,19 +160,19 @@ 'lookup-title' => true, 'lookup-title-skip' => true, 'lookup-pattern' => array( 'id' => '<id>.*?:([\w-]]>] 'error' => '<internalReason>(.*?)</internalReason>', 'noexternalembed' => '<yt:accessControl\saction=\'embed\'\spermission=\'denied\'/>', 'id' => 'ytp', 'title' => 'YouTube (Playlists)', 'website' => ';, 'type' => 'pop', 'added' => '<4.0', // - 'pattern' => 'http://(?:(?:www|[a-z]]>]]]+ 'pattern' => 'https?://(?:(?:www|[a-z]]>]]] 'movie' => ';, 'size' => array(480, 385), 'ui-height' => 25, 'fix-html-pattern' => '<object [^>]]>] ), array(Then...Code: [Select]]>]--- Sources\Aeva-Embed.php 2010-11-19 11:29:34.000000000 +-0200+++ Sources\Aeva-Embed.php 2015-05-13 16:00:29.000000000 +-0200@@ -106,13 +106,13 @@ // For each enabled site to the end, attempt to embed for ($upto = 0; $upto < $j; $upto++) { $message = aeva_match($message); // If no active http links remain (making further embedding impossible), then stop- if (stripos($message, '<a href=";) === false)+ if (stripos($message, '<a href="http') === false) break; } // Reverse protections and return the finished embedded content return aeva_reverse_protection(str_replace('<aeva-begin>', '', $message)); }@@ -113,28 +113,28 @@ break; } // Reverse protections and return the finished embedded content return aeva_reverse_protection(str_replace('<aeva-begin>', '', $message)); } } // Tidy up unset($unaltered); // No links remaining? No further embedding possible, so set this variable before we return- if ($reverse === true && stripos($input, '<a href=";) === false)+ if ($reverse === true && stripos($input, '<a href="http') === false) $context['aeva']]>]] return $input; } // Protect noembed & autolink items from embedding *before* BBC parsing - wrap quotes, but don't protect function aeva_preprotect(&$message, $cache_id) {- if ((stripos($message, ';) === false && stripos($message, '') === false) || strpos($cache_id, 'sig') !== false)+ if ((stripos($message, '://') === false && stripos($message, '') === false) || strpos($cache_id, 'sig') !== false) return; global $modSettings, $context; if (!empty($modSettings['cache_enable']]>] {@@ -202,19 +202,19 @@ return; global $modSettings, $context; if (!empty($modSettings['cache_enable']]>] { // Should haven't got here if autolinking of urls is disabled if (empty($modSettings['autoLinkUrls']]>] return $input; // Parse any URLs....- if (preg_match('~;, $input))+ if (preg_match('~https?://|www\.~i', $input)) { // Modified from SMF code, adding support for [center]]>]]] $input = strtr($input, array(''' => '\'', '"' => '>">', '"' => '<"<', '<' => '<')); $input = preg_replace( array( '`(^|[\s>\.(;\'"]]>]]]]]]]]@@ -705,19 +705,19 @@ { // Modified from SMF code, adding support for [center]]>]]] $input = strtr($input, array(''' => '\'', '"' => '>">', '"' => '<"<', '<' => '<')); $input = preg_replace( array( '`(^|[\s>\.(;\'"]]>]]]]]]]] global $context, $modSettings, $txt, $aeva_timer; $aeva_timer = (isset($aeva_timer) ? (int) $aeva_timer : 0) - array_sum(explode(' ', microtime())); if (strlen($message) > 10 & empty($context['uninstalling']]>] {- if (!empty($modSettings['aeva_enable']]>]]+ if (!empty($modSettings['aeva_enable']]>]] $message = aeva_main($message); else { // Removes any noembed $message = aeva_protection( array('noembed' => false),@@ -1070,27 +1070,27 @@ $message = aeva_main($message); else { // Removes any noembed $message = aeva_protection( array('noembed' => false), global $embed_album, $embed_folder, $context, $force_id; $link = preg_replace(array('~\[url=([^]]>]]]]]]]] $thumbs = array( 'YouTube' => array( 'func' => 'youtubeCreateThumb',- 'pattern' => 'http://(?:video\.google\.(?:com|com?\.[a-z]]>]]]]]]+ 'pattern' => 'https?://(?:video\.google\.(?:com|com?\.[a-z]]>]]]]]] ), 'Dailymotion' => array( 'func' => 'dailymotionCreateThumb', 'pattern' => 'http://(?:www\.)?dailymotion\.(?:com|alice\.it)/(?:[^"]]>]] ), 'GoogleVideo' => array( 'func' => 'googleCreateThumb',- 'pattern' => '.(com|com?\.[a-z]]>]]]]+ 'pattern' => 'https?://video\.google\.(com|com?\.[a-z]]>]]]] ), 'GoogleMaps' => array( 'func' => 'gmapsCreateThumb', 'pattern' => ';]]>]] ), 'MetaCafe' => array(]]>
Nao/Gilles
?action=post
Wed, 13 May 2015 14:17:09 GMT
Because PayPal only allows one website to be linked to one e-mail address, I've moved my website to be the new I'm working on. This just makes sense.- Create an account over there.- Go to your profile, and click the Subscriptions link. You should be taken there.- Click to purchase Aeva Media.- You'll be redirected to PayPal. Proceed with your payment.- You'll be redirected to Wedge.org.- You should be receiving an e-mail with a link to the software. If you didn't receive it, just go to the Media section of wedge.org, and look for the "Aeva Media" folder. If you can't find it, please drop me a PM and I'll look into it.- Download the package.- ???- Profit!]]>
Nao/Gilles
?action=post
Mon, 10 Feb 2014 13:02:10 GMT
I have time for here, but till now and posted, I wanted saver as I can post on the forum MEDIA AEVA to see a question I have.Thanks and regards]]>
IpSiLoN
?action=post
Fri, 30 Dec 2011 12:16:48 GMT
First of all sorry if I didn't post in the proper area, but is so hard to find how to create a topic.I've installed SMF 2.0 fresh install, without errors and after I installed Aeva-Media-1.4w without any errors, but when I try to access the admin menu: About or Settings i get "blank pages" so is impossible to be from another mod because is the only mod that I've installed and is installed on a fresh 2.0 SMF.I've try everything, I've uninstall aeva, drop sql tables, reinstall again, but the problem persist.Can someone help me with this bug?10x in advance!]]>
marius
?action=post
Wed, 22 Jun 2011 08:16:14 GMT
There is a fix for YouTube's new short links (youtu.be)pub/off/6583/youtube-using-short-links/ contains the change required.]]>
Arantor
?action=post
Tue, 12 Apr 2011 17:20:00 GMT
there are reports, that the latest version of AEVA 1.4b does not workcorrectly with SMF RC4 and PortaMX.See here:What about the AEVA 2.04 version ?I had no time yet to test this.I will try to test it this night.If anybody else has got those problems or solutions,please post it here.Many thanks.P.S: Was in 2.04 version already the drop-shadow text overlay integratedto mark the uploaded pictures or do I have to do this with another program ?What would be the best freeware program to do this... easily ?I really need drop-shadow text overlay.Without drop-shadow, the text just is barely readable on many pics...Many thanks.Regards, Stefan.]]>
hartiberlin
?action=post
Tue, 09 Nov 2010 20:47:42 GMT
]
JuxtapositionFor some time I've been worried about the course SMF is taking. New issues arose between the SMF team and us this week that just cemented how we felt, so we thought we'd actually announce something that's been going on.We both did our best to maintain a working relationship with the SMF team, and we both feel that we're the ones always expected to compromise, with unpleasant consequences as you've already heard.SadnessThe SMF team has been actively pushing away some of the most important contributors to SMF, such as us, Runic or the team that went on joining Yourasoft in January, simply because we were more vocal than others about the state of SMF and its team.Some of us got bored waiting for changes, and simply left SMF to die by itself. Others wanted to see the SMF software live on and be able to tackle the new challenges that await it. Unfortunately, with the SMF team insisting on keeping SMF compatible with 5-year-old servers and software setups, and the "feature-frozen" state that SMF has been for the last 2 years, it was impossible to even try doing something about it.So, in mid-August, Pete and I started discussing the possibility of branching off from SMF 2.0.SeparationWe figured, we can work together, away from the SMF team, away from the influences of as many wrongs as possible that SMF fell into.To us, the main problem was with the SMF team, and getting rid of that element in the equation would pave the way forward. The idea was really simple: make a fork on our side, where the project managers are also the only developers, and never let anyone get in the way without being sure that they share our vision of the ideal software. Then, make sure to collaborate with the SMF team to share our bug fixes and feature implementations, so that they can also freely be added to the SMF codebase.And without boundaries, everyone's a winner; just think of the possibilities!DivorceOn August 25, we got started on development, and we contacted the team to negotiate a licence to fork SMF. With 2.0 final, it's moving to a BSD licence, forking becomes inevitable anyway, so we figured offering them a way to mostly get rid of us much sooner wouldn't be a bad idea.It was intended in every way to be a friendly fork; as bugs got fixed, the fixes would go back to SMF (both of us fixed things for RC4, for example)The request was ultimately denied, both by the NPO and the LLC. It's understandable, knowing as we do the reasons for the no-forking clause in the licence originally, but knowing the eventuality of licence change - work commenced anyway.DeterminationYes, that's right: we are actively working on a fork of SMF - the licence doesn't prevent us doing that, all it prevents is distributing it and removing the copyright. (And if you think that's not the case, please read the SMF licence again.)If it did prevent private forks, you'd never be able to have private mods and customised sites. As for us, we're just waiting for 2.0 final and the result licence change to be able to go properly public about it.SuggestionBefore, I mentioned a new theme and new features - this was our way of saying that we're working on our fork. These are, or will be, in the fork itself, along with plenty more besides.Lots has been done already - for instance, SMF is filled with compatibility code, changing a feature tends to break something else.We must have pruned close to 15% of useless code by dropping support for many technologies that are either too old, or irrelevant in the SMF landscape: PostgreSQL, SQLite, PHP 4, MySQL 3.x, non UTF-8 character sets and many others. Things like the help manual were removed, because we strongly believe that if someone needs to read a manual to do something, then something's wrong and we should rethink how we do it.PreparationWe did originally plan and agree to keep this quiet, and we're not revealing where the discussion is taking place for the fork, for its features and development, but it isn't here (but on a dedicated, private site.)It is finally time to reveal because the team has shown hostility to both of us, and even more so in the last few days, and we feel it is totally out of line. You already know about Pete's issues with vbgamer45, and the SMF steering committee taking a stand to protect him, even though he's broken pretty much all of the SMF team rules -- several times.Hell, he's been accused of trying to kill SMF. He might as well actually try living up to that claim, but for the right reasons.VilificationI, on my side, had requested for the ?action=credits link to be visible in SMF, as it is currently not even linked at all in SMF. In order to make a point, I moved the SMF credits at noisen.com from the footer to the credits page, and proceeded to link to the credits page from the footer. This was denounced by the SMF team as a licence violation, and as retaliation I was stripped of my credits, SMF Friend status, beta tester membership and access to the bug tracker and SVN... before anyone said anything to me.RetaliationNow, considering that such a behaviour would be perfectly accepted in a few weeks (because of the upcoming license change), and that the copyright was still there (albeit on a different page, but still just as accessible from the footer), and finally considering my role in helping SMF's popularity in the last few years with Aeva, I could hardly be put on the same line as a random user installing SMF and removing the copyright to replace it with their own.What would have happened to Jeff Lewis, one of SMF's original creators, had he installed SMF on his website and removed the copyright? Would he have been banned for that? Oh wait... He'd been banned from the SMF website once before for less than that: questioning the team leadership, along with multiple others (see events in January 2010.)Setting this aside, I didn't mind (much) about the retaliation. I was much more annoyed by the fact that (1) nothing was done to ensure that the credits link would be indeed made active in a vanilla SMF install, (2) the SMF team actually chose to get rid of one of their most active community members ever (without even a warning), instead of discussing the issue with him and listening to his requests (i.e. to make the copyright more meaningful.)Not only that, but the SMF project manager, who is aware of our fork and accepted its very idea (without which we might not have started it, because we really wanted to be friendly to SMF), insisted personally on removing beta and SVN access.What that means is, we can't see some of the new bugs or suggest fixes, nor report anything on the bug tracker, be it bug fixes or feature improvements. The SMF team has, effectively, shunned us from any potential influence over the future of SMF.In short: SMF has turned our friendly fork into a hostile one, just like that.ProtectionBecause of that, our fork will not, initially, receive the same BSD licence that SMF will have at that point; the original SMF code will still be BSD licensed, but the package overall will have a custom licence, because we do not want the team making off with some of the code. If they don't want to share their work, we won't share ours, as simple as that.It won't be ready for public launch until after 2.0 is out, because there is so much we want to do with it that we haven't done yet, but it'll be out probably before 2.1 is ready, and with more features to boot (lots, lots more features, including ones the team would never consider putting in the core.)We originally wanted to release a first version by the time 2.0 Gold is out, but the more we worked on the software, the more we realized we could do to improve on it. So, we simply decided not to give ourselves a time limit. Those of you who are used to using SMF RC's won't be far away from home. Even better, since most complex mods will have to be partly (or completely) rewritten for the fork, we will encourage development techniques that ensure they don't touch the main codebase, which in turn will allow anyone to update betas without losing anything.VisionRemember this is Nao + Arantor, or Arantor + Nao (whichever sounds better ) at the helm - between us we have literally thousands of hours, and tens of thousands of lines of SMF related code under each of our belts.Our fork, while it has only been worked on for a bit over 10 weeks, already has some impressive statistics. 240 commits (some of which add large new features), thousands of new lines of code, huge changes in both the frontend and backend, all within a global patch that would total over 2 megabytes if applied to SMF.AnticipationWe're both committing ourselves fulltime to our project, and not expecting anything in return, if only for people's respect for what we're trying to achieve. That the SMF team themselves is no longer willing to respect us, only reaffirms the feeling that we took the right decision in forking.When the time comes to release our first version, you will be able to install it next to your SMF forum, and compare the two different philosophies. Switching to it will be your own choice. It's been a long time since you've had a choice to make, rather than have a choice imposed upon you, hasn't it? Let's hope it will be the beginning of a beautiful friendship.Minification (for those who want the tl:dr version)We feel screwed by SMF, we got tired of taking it, so we're branching off from 2.0 now in a private repository and will go public once the licence to SMF changes.Common sense - What does this mean for Aeva Media users?Obviously, you all noticed that I slowed down work on AeMe in the last couple of months. This has probably been the hardest thing to do for me -- push the project aside to work on the fork. I'm still working on AeMe and playing with the layout and new features, as you may have noticed. The auto-embedding component of Aeva will be a core feature in our fork. I'm also considering integrating the gallery as well, although we haven't made a clear decision yet.]]>
Nao/Gilles
?action=post
Sun, 07 Nov 2010 13:00:50 GMT
Now, some like Akyhne love my mods so much, that they are willing to insult me and get ridiculed in public, just to avoid uninstalling it from their website (or downgrading to a version I didn't make.)But there are people who, on the contrary, don't like Aeva Media, for whatever reason. I'm absolutely fine with that. I wrote AeMe for myself, not for anyone else. It does what I want it to do. If it doesn't suit you, well...Well, until today I used to say "use SMF Gallery, then. It sucks even more, but there are probably people who'll enjoy it more."Now I won't even say that.Arantor purchased vbgamer45's "Community Suite" package at $250 back in August.He never was able to download it. After months of sending e-mails to vbgamer and asking him to give him access to his software suite, he was simply banned from his forum, and his license was revoked (whatever that means -- he was never able to download that in the first place.)What's interesting is that not only did vbgamer NEVER tell Arantor why he banned him.But he actually kept the $250 for himself.Now, I've always been quite patient with that capitalist pig of an incompetent pseudo-dev, and never even mentioned him here even after all he's done to me in the shadows, but a point needs to be made because he went too far.vbgamer45 is a lying bastard and a thief!Thanks for your attention. (And Pete, I hope you won't mind that I posted this here. I just can't stand still and watch my friends be treated like shit.)]]>
Nao/Gilles
?action=post
Thu, 07 Oct 2010 22:37:13 GMT
]
Back in March, I resigned from my Beta Tester position at simplemachines.org, because I was going nowhere. I wanted to take some time off and decided to end development of Aeva Media as well. Two months later, the SMF team offered me a developer position, after which I also ended up resigning, very angry against the team for their behavior.At the time (July 28), after discussing with users and family, I decided to resume development on Aeva Media, but only on a commercial version of it. The free version would only be getting security updates (if needed.)In order to make a stand against the SMF team, I removed my downloadable packages off their mod site, and replaced them with a link to this website. After a while, instead of asking me whether this was intended, they simply deleted my mods and replaced them with a bastardized version, 100% alcohol free. Yikes. Plus, it was using a name that was confusingly similar to Aeva Media.I didn't appreciate this move on the part of the team, and things went downhill very soon. I managed to have the mod renamed to something else, and the mod page was re-enabled after I re-uploaded the Aeva Lite package. It was a lesser evil for me, as I could leave Aeva Media out of their website and have complete control over its distribution. However, less than a couple of hours after that, they permanently banned me from the SMF website.As a result:- I can no longer update the sitelist on the Aeva mod page. This was the only item I had left on that page originally, because deleting it could break functionality. Users of Aeva Lite should thus be using Aeva Media 1.x as a replacement, if they want to be sure the sitelist is updated automatically and quietly as soon as required. I will later release a new version of Aeva Lite with the auto-embedder additions from Aeva Media, as well as a new sitelist address that doesn't rely on the SMF team's good will.- I can no longer provide support for Aeva Media 1.x on their forum, obviously. They did a lot of changes (such as removing their Aeva Media board and merging all of the support topics into one), but I don't know why they did. The support topic is useless! The mod's author can't even VIEW it! (Well, okay, I can view it next time I change my IP address, but then what does it change...?) So, basically: don't expect support from me on their board. I have nothing else to bring anyway. I will no longer go over there.- I may in the near future open a support topic for Aeva Media 1.x and Aeva Lite over here. This is not the case for now. I need some time off to digest all of this crap.Thank you for your time. And thanks to the SMF team for having so much respect for their ex-developer, author of their most popular plugin, main French translator and most zealous beta tester ever. Now, onto another project... This time, I'll make sure it isn't full of self-adoring ninconpoomps.]]>
Nao/Gilles
?action=post
Sat, 14 Aug 2010 17:31:00 GMT
AeMe 2.x is deprecated. No official support is provided for it. The equivalent of AeMe 3.0 will be provided, for free, in Wedge 1.0.What is Aeva Media 2.x?Ah well, that is a good question, I'd like to thank myself for asking it.As you probably know, Aeva Media is a fantastic (trust me, I know it! ) gallery system for SMF forums. It is entirely free, but things happened, and it became impossible for me to keep maintaining it.I announced that I would stop supporting and maintaining it, but then a few persons indicated that they would be willing to pay for the software if I were to keep maintaining it. After discussing the idea, I decided to go ahead and do it.So, in simpler words, Aeva Media 2.x is the follow-up to Aeva Media 1.x, and it includes the Foxy! add-on directly inside the code (you no longer need to install it separately.)Here's the link to purchase Aeva Media (make sure you have created an account at noisen.com first, and that you're logged in!), and then you can download it on this very board immediately after your purchase. Support is only available to customers.Aeva Media 2.0For SMF 1.1.x and 2.x platforms---------------------------------------------------------Created and developed by Nao [noisen.com]]>]Main FeaturesEVERYTHING- It might seem obvious, but AeMe 2.x has all the features in AeMe 1.x... And adds the following:USER PLAYLISTS- Give membergroups the permission to create user playlists. Allowed users will be able to create playlists by simply visiting any item page and clicking the Playlists drop menu and then select "Add to Playlist". Organize your favorites easily and browse them like an album!JAVASCRIPT+FLASH PLAYLISTS- Show nice little Flash-powered playlists in these topics, or pretty much anywhere else, based on user playlists or anything you want (one or more items, one or more albums...)- Make your own Foxprog () clone in a minute (or ten.) Visit the site to see a demo of playlists applied to a music website. Remember you can also do this for video or picture websites, the limit is your imagination!LINKED TOPICS- Create (or not) a linked notification topic automatically when adding/editing an album. You can use this to close per-item comments and have everyone comment on albums instead, or subscribe to topic notifications, or harness the power of other topic-related mods.- A linked topic's first message will feature a Javascript+Flash playlist of its related album. Any new item (or group of items, if you use Mass Upload) will also be added as a new message, allowing to 'bump' the topic. Each time you create a new album, your preference for linked topics will be remembered (i.e., the latest board you posted to will be selected by default, or no album if you choose not to use the feature the previous time.) Whether you locked the previous topic or not will also be remembered.SMG BUTTON- Add a SMG button to the post area, which opens a popup that will allow you to upload an item and insert it into your message in as few clicks as possible on SMF2.EXTERNAL PICTURE EMBEDDING WITH LOCAL THUMBNAIL & PREVIEW- Embed pictures hosted on another server (Picasa, Photobucket, Imageshack, anything you can think of). Thumbnails and previews will be created as needed, but the main files themselves will always stay hosted remotely. For this to work as expected, the Aeva mod needs to be installed, and it is advised to enable Aeva's "External embedding" feature as well.RSS FEEDS- All albums and items now offer RSS feeds to keep you updated for: * Latest items - user profiles, albums, album with children, or the entire gallery. * Latest comments - items, user profiles, albums, album with children, or the entire gallery.What you can do with playlists- Click on "Playlists" in the gallery homepage, and select "New Playlist".- Enter a name, and a description. You're nearly done.- Go to any item page in the gallery, and if you want to add it to your playlist, select your playlist at the bottom of the page, and submit. You're done.- After you've added a few items, just go to your playlist page (use the opportunity to see how cool it looks), click on Modify, and you can re-order items inside the playlist.- You can also click on the Comment button to add a personal comment that will show up below the item in the public playlist. Please note that this comment will appear *below* existing author comments for the item. Consider they're your chance to explain why you chose to add that item to your playlist -- just like user lists on Amazon.- And I'm done.How to install- If Aeva Media is already installed, don't forget to uninstall it before reinstalling it! You won't lose any data. (In fact, you'll never lose your data, unless you manually delete the files by FTP.)- Go to your forum's admin area, upload the zip file through the Package manager, install it and follow the instructions.License agreement (no crappy legal details, as usual with me.)- If you did not purchase this software, please be honest and do it.- You can modify the source code all you want.- Whether you modify it or not -- you are NOT allowed to distribute it.- If you are thinking of sharing the source code with someone, don't do it. It's not allowed.- Please do not use this on multiple websites with a single licence. Ask me for authorization if you are looking into doing it. I'm listening and I'm open. I like seeing what people do with my software.Also, if you wish to use this software, you will be bound by the Aeva Media 2.x license agreement.Please make sure to read it online at Changelogv2.04 - October 24, 2010! Fixed order logic within the preparsing chain, to avoid broken br tags when editing album and title descriptions. Wink, wink, nudge, nudge.v2.03 - October 7, 2010! Fixed a security issue.! Fixed a potential crash during upgrade.+ Added mention in the readme about possible file corruption when doing FTP transfers- Removed support for deprecated functions (setInnerHTML, doUBBC) and browsers (IE4, IE5 Mac)* Tweaks to SMF2 RC3 styling to accomodate for the future.! Fixed to the menu system, in case submenus are added.v2.02 - August 28, 2010* Rewrote YouTube embedding to use their data API. This fixes permanently broken lookups after a certain number of videos were embedded.* If a YouTube video is no longer available, a red exclamation mark will now indicate it next to the video's title.* If an item description is short enough, center it on the page, instead of left-aligning it. The limit is hardcoded to 200 characters.! If an item's filesize was changed after it was uploaded, Aeva Media will show a warning. This usually means that the admin attempted to re-upload pictures but did it in ASCII mode, rather than Binary.! Random items in homepage are now shown as a filestack if requested.! Fixed broken comments area when using code tags inside a comment.! Fixed broken captions when using the SMG tag on a SSI page, if the caption has spaces in it. This is due to admins not preparsing strings as required.! Fixed broken captions when using the SMG tag, if caption had square brackets.! Fixed menu system not working in IE8. (Thanks, spuds!)v2.01 - August 14, 2010+ Replaced the main Aeva Media bar with a nice new dropdown menu system.+ Added automatic thumbnail generator to Google Maps embeds. Wasn't easy!+ Added support for HTML5 audio on audio files, with fallback if incompatible.* Rewrote much of the download manager-type presentation.* Split template into two files, for easier maintenance.+ Added "Icons-only" alternative descriptions to item boxes.+ Added the ability to disable RSS feeds, playlists, comments and ratings.! Fixed search engine logic, as well as page index not showing up in search results.! Fixed string cutter, which, apparently, didn't properly restore entities... Eh?!* Download count is now used as view count if a document can only be downloaded, not viewed.! Fixed various error messages that showed up on strict installs of PHP5. Or something.+ No longer telling you a new version is available, if you're using an unreleased beta.! Fixed aeva_getList() error message and cleaned up most of the Foxy! hook points.- Removed support for BBC News embed, as they made it too complicated. Heck.+ Added support for MP4 files at Ebaumsworld.v2.0 - July 28, 2010+ RSS FEEDS All albums and items now offer RSS feeds to keep you updated for: * Latest items - user profiles, user albums, albums, album with children, or the entire gallery. * Latest comments - items, user profiles, albums, album with children, or the entire gallery.+ SMG BUTTON FOR THE SMF2 MESSAGE EDITOR Add a SMG button to the post area, which opens a popup that will allow you to upload an item and insert it into your message in as few clicks as possible.+ LINKED TOPICS Create (or not) an associated notification topic automatically when adding/editing an album. You can use this to disable per-item comments and force comments on albums instead, or subscribe to topic notifications, or harness the power of other topic-related mods. Any new item (or group of items, if you use Mass Upload) will bump the topic. Each time you create a new album, the latest board you posted to will be selected by default, or no album if you chose not to use the feature the previous time.) Whether you locked the previous topic or not will also be remembered. See the feature in action at Foxprog (