Title: tabloria's Replies | WordPress.org

---

# tabloria

  [  ](https://wordpress.org/support/users/publishly/)

 *   [Profile](https://wordpress.org/support/users/publishly/)
 *   [Topics Started](https://wordpress.org/support/users/publishly/topics/)
 *   [Replies Created](https://wordpress.org/support/users/publishly/replies/)
 *   [Reviews Written](https://wordpress.org/support/users/publishly/reviews/)
 *   [Topics Replied To](https://wordpress.org/support/users/publishly/replied-to/)
 *   [Engagements](https://wordpress.org/support/users/publishly/engagements/)
 *   [Favorites](https://wordpress.org/support/users/publishly/favorites/)

 Search replies:

## Forum Replies Created

Viewing 2 replies - 1 through 2 (of 2 total)

 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Tabloria Searchable Displays] How to generate buttons for links?](https://wordpress.org/support/topic/how-to-generate-buttons-for-links/)
 *  Plugin Author [tabloria](https://wordpress.org/support/users/publishly/)
 * (@publishly)
 * [1 month ago](https://wordpress.org/support/topic/how-to-generate-buttons-for-links/#post-18940575)
 * Hi Robert,
 * I’ve released an update that should make URL fields in card displays easier to
   use for the kind of resource cards you described.
 * In the previous version, using the CSV column header as something like “View 
   the Lesson” was a useful workaround. In the new version, you can set custom link/
   button text separately, so you no longer need to rename the CSV column just to
   control the visible link text.
 * I also added an option to show card URL fields as buttons instead of regular 
   text links. The goal is to make this work reasonably well without requiring custom
   CSS, while still leaving CSS hooks available for users who want to adjust the
   styling further.
 * I wrote a short guide here:
   [https://tabloria.site/blog/card-url-buttons-wordpress/](https://tabloria.site/blog/card-url-buttons-wordpress/)
 * More broadly, I’m still trying to keep Tabloria small and focused while I learn
   which use cases are most useful to people. That’s why I’m being careful about
   larger customization features for now. I don’t want the plugin to become a complicated
   layout builder too early, but I do want to improve the simple, common cases that
   make CSV-based resource pages easier to build.
 * Thanks again for explaining your use case so clearly. It helped me see which 
   improvements would make Tabloria more practical without making the plugin overly
   complicated.
 * Best,
   Andrii
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Tabloria Searchable Displays] How to generate buttons for links?](https://wordpress.org/support/topic/how-to-generate-buttons-for-links/)
 *  Plugin Author [tabloria](https://wordpress.org/support/users/publishly/)
 * (@publishly)
 * [1 month, 1 week ago](https://wordpress.org/support/topic/how-to-generate-buttons-for-links/#post-18937596)
 * Hi,
 * Thank you so much for the kind words and for the clear report.
 * You were right: Tabloria was detecting URL fields, but it was still showing them
   as plain text. You did not miss a setting.
 * I just released **Tabloria Searchable Displays 0.1.45** with a fix for this. 
   After updating, URL columns should appear as clickable links in cards, simple
   data tables, and the admin preview.
 * Only normal `http` and `https` links are rendered, so unsafe URLs are still filtered
   out.
 * There is currently no manual field-type editor in the plugin, so suggestions 
   about changing the field type manually do not apply to the current version. Button
   styling and custom button labels are now on my list for a future update.
 * If the column is already detected as a URL field, updating the plugin should 
   be enough. If it still shows as plain text after the update, please share the
   column header and one anonymized example row from the CSV, and I’ll take a closer
   look.
 * Thanks again for reporting this. This was very helpful feedback for improving
   the plugin.

Viewing 2 replies - 1 through 2 (of 2 total)