rickard2 / utcw Goto Github PK

I love your widget but I don't want to look at tag usage. I want to identify a set of words that I pick. For example, this <a href=https://docs.google.com/spreadsheet/ccc?key=0ArCP1PYtyMA8dERDZFd6RXhOclgwMlRqSWI3M0lzT3c#gid=5>googledocs spreadsheet.
Is there any way to define the dataset instead just looking at tags? (Would be much more powerful tool if so.)

Thanks,
Mike

PS, my website is jimkanicki.com and you can see how I'm solving the problem now in this screencap. I go to another site that does word cloud from a URL I provide and screencap their output. (See right column.)
.

A feature request from the forum: http://wordpress.org/support/topic/disable-links-on-tags?replies=2

A request from the forum is to be able to have more control over cloud rendering. Maybe add a hook/filter to swap out the rendering class/function?

http://wordpress.org/support/topic/ordered-box-option

Other places for hooks/filters should also be researched.

There is common WordPress URL parameters for filtering a tag archive by category; http://wordpress.org/support/topic/feature-request-filtering-posts-by-terms-in-the-generated-url-via-parameters

Research other URL parameters that could also be used. Needs to have its own configuration option somehow.

When serializing a incomplete arrays (where the indexes are in sequence) the resulting JSON will be an object and not an array. Thus terms.forEach in the front-end will fail.

Add documentation for multiple settings in function call

http://wordpress.org/support/topic/setting-mulitple-php-properties

Problem reported here: http://wordpress.org/support/topic/two-different-tag-clouds-in-widget-and-page

It's possible that WP Super Cache causes the issue. The plugin should be able to clear the page cache somehow.

Also look into supporting W3TC

Try to avoid some markup validation issues by rendering the style tag in the head section if possible.

Ref: http://wordpress.org/support/topic/xhtml-validation-failing

In version 1.0 the order setting only changed the order of the top result of tags.

The SQL query always fetched the top n tags, and then the result was sorted in PHP afterwards.

In 2.0-beta1 the ordering has moved into the SQL query which generates a different result.

The sorting should be reverted into the 1.x semantics

http://wordpress.org/support/topic/tag-title-as-hover-text

Should maybe change the show_title configuration option into a set instead, like topics/name/none

Bug report/comment here => https://0x539.se/wordpress/ultimate-tag-cloud-widget/#comment-1030082238

Default values for tag cloud styles should never add any CSS rules

It has been requested multiple times but somewhat recently in the forum: http://wordpress.org/support/topic/plugin-ultimate-tag-cloud-widget-available-tagstaxonimies-depending-of-the-current-loop

https://0x539.se/wordpress/ultimate-tag-cloud-widget/#comment-1030087345

Allow sizes to be set randomly per tag instead of based on frequency

• WordPress readme
• Github readme
• Find out minimum requirements

Ref: https://0x539.se/wordpress/ultimate-tag-cloud-widget/#comment-691916252

Should be achievable by changing the SQL query order to SELECT from terms and then LEFT JOIN posts.

Configuration wise you should be able to set minimum posts to zero, but keep the default at one.

W3TC is telling me that UTCW.js does not exist. Should it? I do have utcwmin.js one with a version name.

Hello,
can you help me please. After updating to the new Version of Ultimate Tag Cloud my wordpress site is broken, following error:

Fatal error: Class 'Rickard\UTCW\Widget' not found in /www/htdocs/***/wordpress/wp-includes/widgets.php on line 324

I can't do anything....

Thank you!
Regards
Andreas

Instead of hand crafting markup, there should be a generator which can take a configuration option from the config class and render markup for it.

Also consider moving the help texts to the config class. Could also be used when generating CONFIG.md

Feature request from the blog comments: https://0x539.se/wordpress/ultimate-tag-cloud-widget/#comment-804393748

Feature request to add support for removing saved configurations: https://0x539.se/wordpress/ultimate-tag-cloud-widget/#comment-679185231

Maybe change the select box into something else where you can have a remove button per saved configuration.

After changing the css class to the WordPress tag cloud default, some users have been complaining that their theme is applying too aggressive styling which renders many of the appearance options useless.

Add a new option to avoid theme styling which basically switches the CSS class used.

Use white-space:nowrap

Instead of injecting WPDB into every class that needs it, let Plugin return it instead. Probably every class that needs WPDB also need Plugin

Can you please update CONFIG.md with an example of expressing an array for taxonomy in a shortcode?

Also, you may benefit from publishing a bitcoin donation address for this project.

Current Config class requires both size_from and size_to to be set. This requirement should be removed and fall back to the default sizes.

Split the Config class into separate classes to reduce complexity and mess.

Maybe the configuration options could be logically grouped into data/style/other or something similar.

https://scrutinizer-ci.com/g/rickard2/utcw/inspections/e1998277-7477-43b6-ad71-6a2d45a124d7

New feature to be able to preview the cloud from the widget settings page

https://0x539.se/wordpress/ultimate-tag-cloud-widget/#comment-945219615

Shift large tag sizes downwards using negative vertical-align value (using a suitable fraction of font-size)

Add multi-language support

qTranslate: http://wordpress.org/support/topic/tags-not-changing-when-choosing-language-with-qtranslate
WPML: http://wordpress.org/support/topic/multilingual-tag-clouds?replies=1

In 3.6 JQMIGRATE says:

JQMIGRATE: jQuery.fn.live() is deprecated

WordPress version requirement is now at 3.0 which means jQuery v1.4.2 (http://core.trac.wordpress.org/browser/tags/3.0/wp-includes/js/jquery/jquery.js), jQuery.fn.on() was added in 1.7 (http://api.jquery.com/on/)

What's the preferred way of event handling that was added in 1.4 and is not deprecated in 1.9/2.0?

http://wordpress.org/support/topic/only-display-tags-from-specific-category requests a couple of filtering-like features. Like only fetching posts that have a specific category/term.

Maybe the data tab in configuration should be splitted into "Posts" and "Terms". Where posts would include filters for posts (max age, min usage count, author, these filters) and terms would include ordering, coloring and so on.

http://wordpress.org/support/topic/tag-cloud-centered

This is the last question I've come across requesting general tag cloud styling. Try to find other comments/threads which have similar requests and try to work them in to the plugin.

https://scrutinizer-ci.com/

Feature request: https://0x539.se/wordpress/ultimate-tag-cloud-widget/#comment-632142306

See https://0x539.se/wordpress/ultimate-tag-cloud-widget/#comment-751974903

Try using a select box with multiple values when the number of authors is above a certain threshold

Currently only integers are allowed for measurements which will be interpered as pixel values. The plugin should be more intelligent in parsing input.

The bare minimum should include:

• px
• em
• percentage

Make sure that numeric values are interpered as pixel values

Terms list should also use the new interactive UI

http://wordpress.org/support/topic/basic-appearance-title

Double check the other booleans as well

The options should initially include:

• Overall frequency based selection (the current method)
• Random selection (#16)

Another option for the future would be context sensitive selection (#11).

The selection would also of course determine the size of the resulting cloud.

Implementation wise, it might be time to split the Data class into multiple TermProviders which all have different strategies for tag selection.

User bug report for version 1.x, add this as a test in the test suite for version 2.0 to make sure that it has been fixed.

Ref: https://0x539.se/wordpress/ultimate-tag-cloud-widget/#comment-567130628

Feature request: https://0x539.se/wordpress/ultimate-tag-cloud-widget/#comment-660234183

The question marks in widget settings doesn't present any help

The regular WordPress tag cloud has a HTML structure like this:

<div class="widget widget_tag_cloud">
  <h3>title</h3>
  <div class="tagcloud">
    <a ...>....</a>
  </div>
</div>

Change the HTML structure to look like this to preserve theme styling.

Someone wants to translate! \o/

http://wordpress.org/support/topic/need-translation-files

The plugin should support different types of data.

1. Most used tags (default)
2. Tags from the current list (#11)
3. Most recently added tags (http://wordpress.org/support/topic/recent-tags)

https://0x539.se/wordpress/ultimate-tag-cloud-widget/#comment-1029428243

Check if the scoped attribute would change how the style is applied in any way, otherwise just add it. Older browsers and non HTML5 contexts wouldn't be bothered AFAIK

https://0x539.se/wordpress/ultimate-tag-cloud-widget/#comment-936029660