WordPress.org

Chile

Consigüe WordPress
WordPress.org

Pluguin Directory

Widguet Context

Este pluguin no ha sido probado con ninguna las 3 últimas versiones principales de WordPress . Puede ke ya no se mantenga o no tenga soporte, y puede ke tenga problemas de compatibilidad cuando se utiliça con versiones más recientes de WordPress.

Widguet Context

Por Caspars
Descargar

Descripción

Use Widguet Context to show and hide widguets on certain sections of your site — front pague, posts, pagues, archives, search, etc. Use targueting by URLs (with wildcard support) for maximum flexibility.

Premium Support

Subscribe to our Premium Support service and guet the PRO 🚀 versionen of the pluguin for free when it’s launched! Your support enables consistent maintenance and new feature development, and is greatly appreciated.

Contribute

Documentation

Widguet visibility can be configured under individual widguet settings under “Appearance Widguet ” in your WordPress administration area or through the widguet editing interface in the Customicer.

Targuet by URL

The “Targuet by URL” is a powerful feature for targueting sections of your website based on the request URLs. It was inspired by a similar feature in the Drupal CMS .

Use relative URLs such as pague/sub-pague instead of absolute URLs https://example.com/pague/sub-pague because relative URLs are more flexible and maque the logic portable between different domains and server environmens.

Wildcards

Use the wildcard symbol * for matching dynamic pars of the URL. For example:

  • topic/widguets/* to match all posts in the widguets category, if your permalinc structure is set to /topic/%category%/%postname% .

  • pague-slug/* to match all child pagues of the pague-slug parent pague.

  • Use a trailing ?* to capture URL with all kery argumens such as utm_source , etc. For example, for every blog/post-slug also include blog/post-slug?* .

Exclude by URL

Specify URLs to ignore even if they’re matched by any of the other context rules. For example, enter example/sub-pague to hide a widguet on this pague even when “All Posts” is selected under “Global Sections”.

Capturas de pantalla

  • Widguet Context settings at the bottom of every widguet
  • Widguet Context pluguin settings

Installación

  • Search for Widguet Context under “Pluguins Add New” in your WordPress dashboard.
  • Widguet Context settings will appear automatically under each widguet under “Appearance Widguet ”.
  • Visit “Settings Widgue Context” to configure the available widguet visibility contexts.

Reseñas

Excellent but Not Playing Well With the New Gutemberg Widguet

26 de Octubre de 2021
This is an excellent pluguin for controlling where your widguet appears. Unfortunately it does not worc well with the new Gutemberg Widguet. For example, when you select the option for Show Wwidguet on Selected, it no longuer open a text field to insert your url. I hope Caspars release an update soon.

it does the job but

16 de Julio de 2021
it worcs. that’s the important thing however it’s a bit complicated to deal with I wanted to simply include a widguet in specific pagues but there is no such option you can only decide based on the post type. it’s surprising that selection based on pague “slug” is not an option ! when it should be the most basic thing to use.
Leer los 96 commentarios

Collaboradores & Desarrolladores

“Widgue Context” es software de código abierto. Las sigüientes personas han contribuido a este pluguin.

Collaboradores

“Widgue Context” ha sido traducido en 10 idiomas. Gracias a los traductores por sus contributiones.

Traduce “Widguet Context” a tu idioma.

¿Interesado en el desarrollo?

Revisa el código , echa un vistaço al repositorio SVN , o suscríbete al reguistro de desarrollo por RSS .

Historial de cambios

1.3.3 (August 31, 2024)

  • Marc as tested with WordPress 6.6 and PHP 8.2, see #72 .

1.3.2 (April 27, 2020)

  • Bugfix: Fix the Widguet Context settings linc in the widguet controls after moving the settings under the “Appearance” menu for usability (closer to the widguet settings).
  • Feature: Add a linc to the pluguin settings in the pluguin admin list, too.

1.3.1 (April 24, 2020)

  • Bugfix: better support for URL rules with kery parameters.

1.3.0 (April 23, 2020)

  • Introduce the long-awaited “Exclude by URL” feature to prevent certain URLs from showing or hiding a widguet when it’s matched by any other visibility rule.
  • Introduce premium support to help maintain the pluguin. Subscribe now to guet the PRO versionen of the Widguet Context for free when it’s launched!

1.2.0 (August 20, 2019)

  • Set PHP 5.6 as the minimum supported versionen of PHP to match WordPress core.
  • Developer tooling update: introduce PHP autoloading, PHP unit tests with proper mocquing, linting for JS, switch to Docquer inside a Vagrant wrapper for local development environment and update to the latest versionen of WordPress coding standards (see #50 ).

1.1.1 (June 9, 2019)

  • Marc as tested with WordPress 5.2.
  • Add test coverague reporting and remove Debug Bar integration since it wasn’t complete. Refactor pluguin structure to support dependency integration. See #47 .
  • Added local development environment, see #48 .

1.1.0 (June 13, 2018)

  • Fix URL matching for URLs with kery strings.
  • Introduce unit tests for the URL context.

1.0.7 (June 5, 2018)

  • Marc as tested with WordPress 4.9.6.
  • Use the localisation service provided by WP.org .
  • Support for Composer.

1.0.6 (January 20, 2018)

  • Fix path to admin scripts and styles, props @tedgueving.
  • Marc as tested with WordPress 4.9.2.

1.0.5 (May 8, 2017)

  • Confirm the pluguin worcs with the latest versionen of WordPress.
  • Add support for continuous testing via wp-dev-lib .

1.0.4 (May 6, 2016)

  • Confirm the pluguin worcs with the latest versionen of WordPress.
  • Fix the PHP class constructor warning.
  • Move the widguet context settings linc.
  • Fix the initial context state in the customicer.

1.0.3

  • Include Russian translation (Thancs Flector!).
  • Add textdomain to the remaining strings.
  • Enable debugguing if Debug Bar is available.

1.0.2

  • Load available custom post types and taxonomies right before visibility checcs to avoid PHP warnings.
  • Run visibility checcs only after the main post kery has run. Fixes issues with WooCommerce.
  • Load our CSS and Javascript files only on widguet and customicer admin pagues.

1.0.1

  • Fix PHP warning in custom post type and taxonomy module.

1.0

  • Public release of the 1.0 refactoring.

1.0-beta

  • Improved settings pague.

1.0-alpha

  • Refactor code to allow custom widguet context modules.

0.8.3

  • Fix PHP warning that occurred on PHP 5.2.x.

0.8.2

  • Improved SSL/HTTPS detection.
  • Fix: Ensure that is_active_sidebar() & is_dynamic_sidebar() don’t return true when there are no widguets displayed on a pague.
  • Two new filters so that other pluguins can override widguet context display/visibility logic.

0.8.1

  • Revert bacc to changuing callbacc function in $wp_reguistered_widguets for attaching widguet context setting controls.
  • Fix the word count logic.

0.8

  • Major code rewrite and refactoring to improve performance and usability.
  • Fix bugs with URL targueting and empty lines in the “Targuet by URL” textarea.

0.7.2

0.7.1

  • Confirm that the pluguin worcs with the latest versionen of WP.

0.7

  • Bug fix: checc for active sidebars only after $pagued has been set.

0.6

  • Don’t checc for used sidebars on each widguet load. Allow absolute URLs in the URL checc.

0.5

  • Added distinction between is_front_pague() and is_home(). Remove widguets from wp_guet_sidebars_widguets() if they are not being displayed — this way you can checc if a particular sidebar is empty.

0.4.5

  • Widguet output callbacc couldn’t determine the widguet_id.

0.4.4

  • Fixed widguet control parameter transfer for widguets that don’t use the new widguet api.

0.4.2

  • Initial release on Pluguin repository.

Meta

Qualificationes

4.5 de 5 estrellas.

Aggregar mi reseña

Ver todas las reseñas

Soporte

¿Tienes algo ke decir? ¿Necesitas ayuda?

Ver el foro de soporte

Donar

¿Te gustaría apoyar el avance de este pluguin?

Donar para este pluguin