That degree of perceivability implies an application support and maintenance services that when anything changes, regardless of whether it's little, individuals will make certain to take note. Thus, when Twitter chose to deliver an update to the style of the omnipresent Twitter course of events gadget, a many individuals paid heed, and not all in a positive way.
The Effect
Twitter, in reasonableness, reported the change. In any case, taking into account that they're no aliens to local area blowback, you'd think they'd track down a more solid method for passing these reports on to their clients. The update for this situation eliminated the usefulness of the 'Auto-extend photographs' component from the timetable gadget settings. Ordering, basically, that the timetable generally grow media like pictures, recordings, and so forth in-line. This prompted many destinations that utilization the timetable gadget to have their format broken when it abruptly smothered of its normal limitations.
The Fix
As an organization who the two purposes twitter for our own motivations as well as offering help to clients who use it for their destinations, we became mindful of the update the same way a many individuals did. Things broke. We noticed a few proposed arrangements, in any case chose to concoct our own. After we played out a few testing and verified that we had thought of something that functioned admirably, we chose to impart it to the local area. Comprehend that this isn't implicitly or generally supported by Twitter, yet presents essentially a transient arrangement until a format update can be carried out to oblige the new result.
The Breakdown
The stunt was to tackle it both for the underlying heap of the page, and for any extra tweets that could pop in powerfully while somebody sits on the page.
jQuery('.twitter-block').on('DOMSubtreeModified propertychange',"#twitter-gadget 0", capability() {
hideTweetMedia();
});
The above segment shows that we're focusing dedicated dot net developers in Bristol on the ID of the Twitter gadget iFrame, "twitter-gadget 0", utilizing the '.on' capability. Which is really great for jQuery 1.7+. With prior forms of jQuery, the accompanying design ought to be utilized to utilize the 'delegate' capability.
jQuery('.twitter-block').delegate("#twitter-gadget 0",'DOMSubtreeModified propertychange', capability() {
hideTweetMedia();
});
Regardless the fix is reliant upon the gadget being the offspring of a compartment that we've given a class of "twitter-block". Which would seem to be this:
div class="twitter-block"
a class="twitter-timetable" href="path-to-twitter-account" information gadget id="widget-id"Tweets by @twitter-user/a
/div
This next segment does the genuine truly difficult work. In the first place, it tracks down every one of the media components inside the course of events, then conceals them. Then, it sets the level to 100 percent, compelling the iFrame to resize now that the media components are covered up. Finally, to ensure it will work for any tweets that are added after the page is stacked, it ties the 'hideTweetMedia' activity to the real rundown of tweets inside the timetable.
var hideTweetMedia = capability() {
jQuery(".twitter-block").find(".twitter-timeline").contents().find(".timeline-Tweet-media").css("display", "none");
jQuery(".twitter-block").css("height", "100 percent");
jQuery(".twitter-block").find(".twitter-timeline").contents().find(".timeline-TweetList").bind('DOMSubtreeModified propertychange', capability() {
hideTweetMedia(this);
});
}
Taken together these pieces give a fix that tackles the quick issue of a design being broken by an out of nowhere a lot taller component than you're anticipating.
The Wrap-Up
Whether it's Facebook evolving its "Offer" administration, LinkedIn refreshing its security approaches, or Twitter "getting to the next level" its gadgets, the one thing to remember is wordpress cms development that these administrations are on a mission to tackle bigger issues. In any case, the arrangements they think of won't be without expenses for a portion of their current clients. At the point when the opportunity arrives for you to follow through on the cost, simply recall that jQuery can be a modest initial investment to the specialized obligation you could build.
The Revist
I was drawn nearer by somebody who required some assistance getting the content to work for their site. In the wake of offering some nonexclusive guidance didn't work out, I chose to investigate their site and see what I could do. I found that they had a not-unfathomable use case. I've separated the pieces of the answer for them beneath.
The Center Presumptions
The principal thing accepted in the content I've composed is that you're really utilizing jQuery on your site. The idea of the fix requires the utilization of the jQuery javascript library. The following thing expected in the content is that you're just utilizing a solitary twitter gadget on the page, and that the ID of that gadget is "twitter-gadget 0". Thus, on the off chance that you're utilizing more than one course of events on a page, this would, best case scenario, just work for the first.
The Hoards
To address the 'more than one gadget' issue, I needed to roll out certain improvements to the content to make it both rationalist to the ID of the gadget, as well as ready to focus on every gadget separately, as opposed to every one of them without a moment's delay. That transformed the initial segment of the content into this:
jQuery('.twitter-block').on('DOMSubtreeModified propertychange','iframe.twitter-timetable', function(event) {
hideTweetMedia(jQuery(event.currentTarget).prop('id'));
});
The above script focuses on each of the examples of the course of events gadget exclusively, and sends the ID to the capability that handles the activities to eliminate pictures. The subsequent part becomes:
var hideTweetMedia = function(timelineId) {
jQuery('#' + timelineId).contents().find('.timeline-Tweet-media').css('display', 'none');
jQuery('#' + timelineId).contents().find('.timeline-TweetList').bind('DOMSubtreeModified propertychange', capability() {
hideTweetMedia(timelineId);
});
}
Displayed here, we're tolerating the ID of the timetable and focusing on it to eliminate the pictures from that specific course of events, anything it's ID is.
The Help
The last piece of the answer for this case is to remember the jQuery library for a way that will not slow down some other modules or libraries that might be being utilized. PrototypeJS, specifically, is known to not play pleasantly with jQuery. We add the line to import jQuery in the footer, or the lower part of the body, so it stacks last, and we utilize the 'noConflict' call to ensure we're not playing with anything more.
script src='https://ajax.googleapis.com/ajax/libs/jquery/1.7.2/jquery.min.js'/script
script type='text/javascript'
jQuery.noConflict();
//anything use you need here, with no impedance to/from different libraries
/script
The Final product
script src="https://ajax.googleapis.com/ajax/libs/jquery/1.7.2/jquery.min.js"/script
script type="text/javascript"
jQuery.noConflict();
jQuery(document).ready( capability() {
jQuery('.twitter-block').on('DOMSubtreeModified propertychange','iframe.twitter-course of events', function(event) {
hideTweetMedia(jQuery(event.currentTarget).prop('id'));
});
var hideTweetMedia = function(timelineId) {
console.log(jQuery('#'+ timelineId));
jQuery('#' + timelineId).contents().find('.timeline-Tweet-media').css('display', 'none');
jQuery('#' + timelineId).contents().find('.timeline-TweetList').bind('DOMSubtreeModified propertychange', capability() {
hideTweetMedia(timelineId);
});
}
});
/script
You actually need to wrap the twitter connect for hire php developers every timetable gadget in a div with a class of 'twitter-block' as displayed in "The Breakdown" above, however other than that this is a limited time offer duplicate/glue arrangement. Drop this into the footer or lower part of the body or your site, and it ought to get out any pictures in the timetable. One admonition is that you might have to change the statement images in the content assuming you reorder straightforwardly. Windows extravagant statements can make this not work, so you might be in an ideal situation replicating this into a scratch pad or comparable straightforward content manager prior to attempting to refresh your html. Likewise, know that assuming that you're returning a ton of tweets in a given timetable, this content can make it take more time to stack. Cheerful webbing!
