I dont understand - once you clear the browser cache this issue does not
exist

On 2 July 2015 at 19:04, Thomas Hunziker notifications@github.com wrote:

Issue

The quickicon plugin which checks for Joomla Updates shows the message
twice.

Expected
[image: expected]
https://cloud.githubusercontent.com/assets/1018684/8483941/b08bcfa2-20f4-11e5-900a-416930bfa77b.PNG
Actual
[image: actual]
https://cloud.githubusercontent.com/assets/1018684/8483943/b46a6624-20f4-11e5-8c31-44374e093876.PNG
Solution and Background

The JavaScript code which adds this message checks for a in the
specific ID of that plugin output and adds the message there. This worked
fine as long as there was only one there. Now we changed the icons
to use the tag instead of and guess what, now there are two
tags in there. You don't need to be a JavaScript guru to
understand what now happens [image: ]
The solution is to not target the tag itself but the specific
class of that
Testing

Best test with a Joomla 3.4.2 before updating to 3.4.3.

You can view, comment on, or merge this pull request online at:

#7323
Commit Summary

• [fix] Removes the duplicated "Update to Joomla x.y.z" message in the quickicon.

File Changes

• M media/plg_quickicon_joomlaupdate/js/jupdatecheck.js https://github.com/joomla/joomla-cms/pull/7323/files#diff-0 (2)

Patch Links:

• https://github.com/joomla/joomla-cms/pull/7323.patch
• https://github.com/joomla/joomla-cms/pull/7323.diff

—
Reply to this email directly or view it on GitHub
#7323.

Brian Teeman
Co-founder Joomla! and OpenSourceMatters Inc.
http://brian.teeman.net/

Nah, has nothing to do with browser cache.
jQuery('#plg_quickicon_joomlaupdate').find('span').html(updateString); will update each <span> within the tag with the attribute "id=plg_quickicon_joomlaupdate".
The HTML structure for the quickicon is like this:

<li id="plg_quickicon_joomlaupdate">
    <a href="index.php?option=com_joomlaupdate">
        <span class="icon-joomla"></span>
        <span class="j-links-link">Unknown Joomla! ...</span>
    </a>
</li>

See the two <span> tags there?
The icon one comes from
https://github.com/joomla/joomla-cms/blob/staging/layouts/joomla/links/link.php#L21
and the content one from
https://github.com/joomla/joomla-cms/blob/staging/layouts/joomla/links/link.php#L16

must have been an earlier issue then with the same outcome but for a
different reason

On 2 July 2015 at 20:58, Thomas Hunziker notifications@github.com wrote:

Nah, has nothing to do with browser cache.
jQuery('#plg_quickicon_joomlaupdate').find('span').html(updateString);
will update each within the tag with the attribute
"id=plg_quickicon_joomlaupdate".
The HTML structure for the quickicon is like this:

Unknown Joomla! ...

See the two tags there?
The icon one comes from

https://github.com/joomla/joomla-cms/blob/staging/layouts/joomla/links/link.php#L21
and the content one from

https://github.com/joomla/joomla-cms/blob/staging/layouts/joomla/links/link.php#L16

—
Reply to this email directly or view it on GitHub
#7323 (comment).

Brian Teeman
Co-founder Joomla! and OpenSourceMatters Inc.
http://brian.teeman.net/

Maybe, yes.

I noticed this behaviour a few days ago and deleting the cache seemed to solve the problem. Now that I logged in again, it´s obvious that the problem persists.
After applying this patch the duplicated message is gone. Logging in again, everthing is fine.

@test success! Thanks!

same issue on extensions check

Ah, I did know that I had cleared and cleared browser cache and all caches possible. Almost cleared my OS to get rid of the double message...

I do not have the issue on extension check here.

Thank you @Bakual, this fixes the bug. -> RTC

Merged! Thank you @Bakual.

@810

same issue on extensions check

Can you point us to the check? I'm not sure what do you find on the extensions check see: https://github.com/joomla/joomla-cms/blob/staging/media/plg_quickicon_extensionupdate/js/extensionupdatecheck.js

same issue on extensions check

If it is, then it's a different issue. Did you try with clearing the browser cache?

the same fix did the trick, so its ok now