Jump to content

~AR

Approved members
  • Content Count

    7
  • Joined

  • Last visited

  1. Andrew, could you post a documentation as to deploying a JS + CSS that would be the "Revive Recommended Version" for an intermediary fix? A Step-by-step guide we ALL use when confronted with the issue, so all Revive users are working off the same solution. That would allow for better bug reports, trouble shooting, etc. Because right now it is fragmented, everyone is using a different solution and there is no common ground on the matter, so no real forward progress can be made. I see that as an in between step that would still allow functionality in the current release, while development progresses on a true async solution.
  2. Thanks Andrew for your reply. As the starter of, what has become a wildfire of a thread here, I thought I'd chime in. I've been monitoring the progress of this thread since I posted it and I still believe Asynchronous loading should be a top priority and is vital to speeding page load speeds. And if Revive wants to be at the forefront of ad servers (which it should be), it needs to be built in. As Redstorm stated above, page rankings are severely affected by page load times. Yes, coders have always been able to modify, work-around or adapt, as some suggestions have been posted (which by the way are great work in the right direction), but ultimately, universal usability is going to be the Revive strong point. Create something that doesn't get in the way of the design and usability (non-asyc currently does just that) and your market for developers has then opened up to nearly anyone looking for a competent alternative. I can't stand Google DFP, OpenX is a joke (don't even get me started), and what are you really left with? Revive has a chance to become the Unix/Unbuntu of the ad server world, but maintaining universality will be key in keeping the project at the top of the list. I have been using OX, OAds, etc since it was still PHPads (can't recall what generation it was when I first started using it, but since early 2000s) and believe, it has the potential to be a far better ad server over the "services" provided out there. Sans the monetized atrocity that OpenX became, OpenAds/Revive has always been about being the ad server that WORKS for those that don't want to use the alternative "services" out there. No site admin wants to research, rewrite, or modify the invocation codes, they simply want to put it in place and manage inventory, and not have to be concerned that their "workaround" may break or degenerate to an unusable state, because the software is updated or changed. Make it work, make it work right, keep it transparent within a site, and make it so ANYONE can use it.
  3. Is the Revive (or older versions of OX) suseptable to the Heartbleed vulnerability? With the open door in the OpenSSL, I just need to know if I should be patching something on my ad servers ASAP. Thanks! ~AR If you're not aware: http://heartbleed.com/ more info: http://www.zdnet.com/heartbleed-bug-affects-yahoo-imgur-okcupid-convo-7000028213/ http://blog.sucuri.net/2014/04/patching-the-heartbleed-openssl-vulnerability.html online checker: http://rehmann.co/projects/heartbeat/
  4. thanks all! I had left off with looking into how to rewrite the invocation code to eliminate the 'document.write' command following the outline on the article here: http://www.stevesouders.com/blog/2012/04/10/dont-docwrite-scripts/ and http://www.stevesouders.com/blog/2010/12/15/controljs-part-3/ but being that this isn't my primary job, and that I'm mainly self-taught when it comes to javascript, I wasn't comfortable with putting it into practice. perhaps someone else can pick up the mantle? i've got to assume that creating a async version of the invocation code for an ad server would be highly beneficial. Especially since they are notoriously blamed for slow page load times, and almost entirely use the document.write statement which prevents/stops async loading of pages. ultimately, ads should be seemless on a page, not affecting load times. I know real-world case isn't going to be 100% non-interferance, but anything closer, I've got to imagine is going to be benificial and give an edge in the industry. Besides, isn't Revive all about reviving the ad server software world?
  5. Hello, Looking for a way to asychronously run the invocation code to prevent ad loading from delaying page load times. I had looked into it previously, but ran into a roadblock because of the way the original OpenX call is structured. I believe it had something to do with the 'document.write' command IIRC. (It has been almost a year since I reviewed working around the problem, so I may be off.) Our company sites have a high saturation of ads all hosted on our servers (no third-party ads) and load times at times really slow the page down. If anyone can build this feature out, that would be tremendously helpful! And if you can code it for a Wordpress Widget plugin (possibly based off the OpenX-WP Widget) that would be even better!
  6. Hello Revivers, I have an OX ad server (v2.8.9) I create at work and it's running ads for multiple sites (all our branded sites - 5-6 total). One of the sites is a Wordpress site using a OpenX-WP Widget plugin. Before I upgrade the server to Revive 3.0.0, does anyone know if the calls made by the OpenX-WP plug-in will still function with the revive 3.0.0 upgrade? Here is a link to the WP plugin page: http://wordpress.org/plugins/openx-wordpress-widget/ If not, can anyone point me in a direction for a Wordpress Revive plugin? Ideally something that is asyncronous, since the current plugin is not and does blog load times on the pages with heavy ad placement. If someone needs an example of the WP widget code, let me know, I'll copy/paste whatever is needed.
×
×
  • Create New...