Jump to content
adrian

Tracy Debugger

Recommended Posts

The new Console panel fullscreen mode now has keyboard shortcuts to collapse the code or results panes quickly.

Here you can see me toggling all code, all results, and the split of both.

Shortcuts are:

CTRL+SHFT+ 

Up arrow - collapses code pane
Down arrow - collapses results pane
Left arrow - to restore split to what it was before you initiated any pane collapses.

Hopefully you'll find this a really quick way to get to the view you need.

rlLAPv47u9.gif.0f3c122f4c276e2f3833fd9971ed6d46.gif

  • Like 4

Share this post


Link to post
Share on other sites

New version fixes a few bugs in the last release, especially regarding the keyboard shortcuts on Windows. Along these lines, I have also changed the shortcuts for the History Stack - they are now ALT+PageUp and ALT+PageDown. This means there is no longer the need to use the meta key (CMD or WIN key) for this which was conflicting on some systems. If you're on a Macbook without PU and PD keys, just use: fn + ALT + PageUp/Down

A big thanks to @Robin S for helping with all the Windows testing on this!

I think this is really starting to work really nicely now - I almost want to use it over my code editor 🙂

Anyway, please let me know if you find any issues.

  • Like 2

Share this post


Link to post
Share on other sites

Hi Adrian,

Does the "User dev template" feature do anything with _main.php if using the delayed output strategy?

If not, what do you think about adding a feature where _main.php is replaced with _main-dev.php if that file exists? Of course the relevant file names would depend on what is defined in $config->appendTemplateFile and the Tracy "User dev template suffix" setting. And to round things out I guess do the same for $config->prependTemplateFile (_init.php).

Share this post


Link to post
Share on other sites
13 hours ago, Robin S said:

Hi Adrian,

Does the "User dev template" feature do anything with _main.php if using the delayed output strategy?

If not, what do you think about adding a feature where _main.php is replaced with _main-dev.php if that file exists? Of course the relevant file names would depend on what is defined in $config->appendTemplateFile and the Tracy "User dev template suffix" setting. And to round things out I guess do the same for $config->prependTemplateFile (_init.php).

Hey @Robin S - it didn't, but now it does 🙂

I have also implemented this for the User Bar Page Versions feature and the Template Path panel. These three things do almost the same thing, but for different users in different scenarios.

I am going to PM you a copy of this new version to take a look at. I have some other things I am working on and I want to commit altogether.

  • Like 1

Share this post


Link to post
Share on other sites

Various significant updates today.

As per @Robin S's suggestion above, the User Bar Page Versions, User Dev Template and Template Path panel features now support automatic swapping out of the files included via `$config->prependTemplateFile` and `$config->appendTemplateFile` to use the same suffix at the replaced template, eg `_init-dev.php` or `_main-dev.php` if you are on the home page and using a home-dev.php template file replacement.

Robin also helped me track down a critical bug that was introduced to Page Versions and User Dev Templates some time ago - thanks for that!

If you haven't checked out any of these features in Tracy before, they can be very handy for testing changes (especially on a live site). In particular, giving your clients access to choose from a dropdown of template options can be a very easy way to get their feedback on various options.

I have also made several improvements to the new Console panel fullscreen editing experience and also updated the way the results pane scrolls when new items are added. Previously it always scrolled to the bottom of the pane. Now it scrolls to the top of the recently added section, so if you are using Clear & Run, then it will alway be at the top, but if you just Run to add new items, it will scroll down to the top of the new items. Hopefully you'll all find this a nice improvement and will help to reduce your scrolling.

I recently noticed some nasty issues with the Console panel in Safari, especially the new fullscreen editing mode, but also when trying to manually resize the panel. Everything looks/works great on Chrome, Firefox, and Opera. I'll take another look and see what I can do about getting Safari to play nicely, but sometimes I feel like Safari is the new IE 🙂

 

  • Like 3

Share this post


Link to post
Share on other sites

Ok, I officially hate Safari more than I already thought I did 🙂

I have fixed a whole range of issues I had never noticed previously (mainly because I rarely use it).

Detailing here in case they are useful for your development in general.

 

1) You can't resize panels smaller than their initial size on page load

I did however fix the internals of the Console not expanding to match a larger panel if you size larger.

The issue is that Webkit browsers will not let you use the CSS "resize" property to resize an element to make it smaller, only larger (in both dimensions): https://css-tricks.com/almanac/properties/r/resize/

Man it took me a long time to figure out why that wasn't working - I thought there was some min-height / min-width type thing going on that was only affecting Safari.

Thank goodness Chrome no longer uses the Webkit engine!

 

2) Safari doesn't play nicely with position: fixed when elements are outside document.body

The Tracy core adds its elements to document.documentElement so the only way I could figure around this was to move the Console panel to document.body when clicking the new fullscreen toggle and then back again when restoring to the panel size. This was also really difficult to track down and I never found any reference to this issue online anywhere - fun times 🙂 

Because the parent element is changed, I had to change the parent element of several css selectors. I can't find anything broken as a result, but please keep an eye out and let me know if you see anything amiss.

 

3) Fix missing inner scrollbar in code editor pane

This one looks to be a long standing Ace Editor bug, but someone else figured out a simple workaround: https://github.com/ajaxorg/ace/issues/2872

 

4) Fixed some keyboard shortcut bugs due to missing e.preventDefault()

Please let me know if you find any other issues like this

 

Anyway, I think I am done with Safari tweaks for now. I am not sure how many of you are even using it for regular development so I don't want to put too much more time into it, but please do let me know if you find anything I missed.

 

  • Like 3

Share this post


Link to post
Share on other sites
2 hours ago, adrian said:

using it for regular development

Are you kidding? 😉

Thanks a million, btw!

  • Like 1

Share this post


Link to post
Share on other sites

One more quick update. In addition to the existing shortcut keys for toggling the size of the code and results panes in the Console panel, I have added a new one:

CTRL + SHFT + → 

Which resizes the code pane to the height of all the lines of code:

EycZvBSDZG.gif.1fa6a8dac547b943637cf06a069a21fa.gif

  • Like 4

Share this post


Link to post
Share on other sites

One more shortcut 🙂

CTRL + SHFT + ENTER will toggle the Console in and out of fullscreen.

 

Totally random, but a little tip about the Console panel - not only is it great for testing the PW API and PHP in general, it's also pretty nice for testing JS code out. Take this example of:

  • calling an external API
  • populating an element in the Console results pane with a property from the returned JSON
  • logging the result to the browser dev console

ctN9oBrlFD.thumb.gif.598b9cab370b2ba85cdc2f10919f3669.gif

 

Why use this over the browser console, or CodePen, JSFiddle etc? Well, notice that the API call is grabbing a PW field from the current page:

'https://represent.opennorth.ca/postcodes/<?=$page->postcode?>/'

 

Also, if you are a fan of the output of the Browser dev console, don't forget about Tracy's fl() option to dump objects direct to this.

Anyway, hope there is something useful there if you hadn't thought about it before 🙂

  • Like 3

Share this post


Link to post
Share on other sites

Hi,

I have installed TracyDebugger on a live website, enabled it, set output mode to Development, and enabled File Editor

but I cannot find the FileEditor e.g. to edit the online template files. What do I have to do to find it ?

 

tracy.jpg

Share this post


Link to post
Share on other sites

My bad sorry. I found the File Editor.

But when I select a template file on the left, the editor window on the right does not update. The editor window on the right stays the same.

Double clicking on a template file on the left does not make a difference, the editor window on the right always shows the same.

tracy-2.jpg

  • Like 1

Share this post


Link to post
Share on other sites
1 minute ago, pwired said:

But when I select a template file on the left, the editor window on the right does not update. The editor window on the right stays the same.

Double clicking on a template file on the left does not make a difference, the editor window on the right always shows the same.

Works for me. Can you please check for JS errors in the browser dev console.

Any difference in another browser?

  • Like 1

Share this post


Link to post
Share on other sites

Is it necessary to have debug = on for the file editor to work ?

I am using FireFox, will try Chrome

Share this post


Link to post
Share on other sites
Just now, pwired said:

Is it necessary to have debug = on for the file editor to work ?

Nope!

  • Like 1

Share this post


Link to post
Share on other sites

Ok the problem must be in my FireFox browser

Edit:
The File Editor is working perfectly in my Chrome browser,
and also in my Opera browser (45.0)

Thanks Adrian

 

Edited by pwired
Tried Opera Browser
  • Like 1

Share this post


Link to post
Share on other sites
Just now, pwired said:

Ok the problem must be in my FireFox browser

The File Editor is working perfectly in my Chrome browser

Good to hear - I'll take a look here with Firefox on Mac and see if I can reproduce and fix it.

Share this post


Link to post
Share on other sites

I am using FireFox Quantum ver 61.0.1 (64bit)

Maybe it has become messed up after so many weeks of heavy use. Will do a clean install and check again.

Share this post


Link to post
Share on other sites

@pwired - I could reproduce with Firefox on MacOS and I have pushed a fix in the latest version. Please let me know how it goes at your end.

New version also removes the keyboard shortcut text from the top of the Console panel and adds a new toggleable popup info table of all shortcuts:

cValA8pRkk.thumb.gif.961039bee582b637e21d26e082f5e677.gif

  • Like 2

Share this post


Link to post
Share on other sites

Hi,

I uninstalled the previous version 4.11.32 and installed the latest version 4.11.34

I can confirm: now it is working in FireFox,

 

Record_2018_09_19_04_41_44_238.gif

 

Thanks, all good.

  • Like 1

Share this post


Link to post
Share on other sites

Another round of tweaks, bug fixes and new features.

1) File Editor revamp to improve layout and adds a new fullscreen editing mode (like the one added to the Console panel), also with the same CTRL + SHFT + Enter shortcut for toggling in and out of that fullscreen.

2) More tweaks and code cleanup for the Console panel.

3) Some nice enhancements and cleanup for the SnippetRunner panel.

4) New "Open" option for the "Goto Page ID" feature in the PW Info panel - this opens the page's branch in the page tree. I find this entire feature very useful when working on sites where the templates make heavy use of IDs instead of paths for querying pages. If you haven't tried, give it a go. 🙂

5) Various bug fixes in the module and also in the Tracy core.

There are quite a lot of changes in this version, so please let me know if you find any issues.

 

 

  • Like 4

Share this post


Link to post
Share on other sites

Another round 🙂

1) I have revamped the fullscreen / halfscreen buttons that are on many of the panels. They have been replaced by a single Maximize / Restore button which I think it much more useful. Hope you guys agree!

2) I have removed the "open in window" link from all panels - I never used this feature and it was painful to get the layout of some of the more complex panels to work in this mode. If others are finding they miss it, let me know and I'll see about reinstating it.

 

  • Like 4

Share this post


Link to post
Share on other sites
11 minutes ago, adrian said:

Hope you guys agree

I did agree a week ago or two too 🙂

Nice updates btw.

  • Like 1

Share this post


Link to post
Share on other sites
1 minute ago, tpr said:

I did agree a week ago or two too 🙂

Nice updates btw.

I know, it was your suggestion that prompted me to make the change 🙂

Sometimes I am slow on coming around to a good idea 🙂

 

  • Haha 1

Share this post


Link to post
Share on other sites

Hey @tpr - sorry I just realized it was a bit rude of me to not acknowledge that change as your idea when I posted about it above.

Sorry about that!

  • Like 1

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By dimitrios
      Hello,
      this module can publish content of a Processwire page on a Facebook page, triggered by saving the Processwire page.
      To set it up, configure the module with a Facebook app ID, secret and a Page ID. Following is additional configuration on Facebook for developers:
      Minimum Required Facebook App configuration:
      on Settings -> Basics, provide the App Domains, provide the Site URL, on Settings -> Advanced, set the API version (has been tested up to v3.3), add Product: Facebook Login, on Facebook Login -> Settings, set Client OAuth Login: Yes, set Web OAuth Login: Yes, set Enforce HTTPS: Yes, add "http://www.example.com/processwire/page/" to field Valid OAuth Redirect URIs. This module is configurable as follows:
      Templates: posts can take place only for pages with the defined templates. On/Off switch: specify a checkbox field that will not allow the post if checked. Specify a message and/or an image for the post.
      Usage
      edit the desired PW page and save; it will post right after the initial Facebook log in and permission granting. After that, an access token is kept.
       
      Download
      PW module directory: http://modules.processwire.com/modules/auto-fb-post/ Github: https://github.com/kastrind/AutoFbPost   Note: Facebook SDK for PHP is utilized.


    • By kongondo
      FieldtypeRuntimeMarkup and InputfieldRuntimeMarkup
       
      Modules Directory: http://modules.processwire.com/modules/fieldtype-runtime-markup/
      GitHub: https://github.com/kongondo/FieldtypeRuntimeMarkup
      As of 11 May 2019 ProcessWire versions earlier than 3.x are not supported
      This module allows for custom markup to be dynamically (PHP) generated and output within a page's edit screen (in Admin).
       
      The value for the fieldtype is generated at runtime. No data is saved in the database. The accompanying InputfieldRuntimeMarkup is only used to render/display the markup in the page edit screen.
       
      The field's value is accessible from the ProcessWire API in the frontend like any other field, i.e. it has access to $page and $pages.
       
      The module was commissioned/sponsored by @Valan. Although there's certainly other ways to achieve what this module does, it offers a dynamic and flexible alternative to generating your own markup in a page's edit screen whilst also allowing access to that markup in the frontend. Thanks Valan!
       
      Warning/Consideration
      Although access to ProcessWire's Fields' admin pages is only available to Superusers, this Fieldtype will evaluate and run the custom PHP Code entered and saved in the field's settings (Details tab). Utmost care should therefore be taken in making sure your code does not perform any CRUD operations!! (unless of course that's intentional) The value for this fieldtype is generated at runtime and thus no data is stored in the database. This means that you cannot directly query a RuntimeMarkup field from $pages->find(). Usage and API
       
      Backend
      Enter your custom PHP snippet in the Details tab of your field (it is RECOMMENDED though that you use wireRenderFile() instead. See example below). Your code can be as simple or as complicated as you want as long as in the end you return a value that is not an array or an object or anything other than a string/integer.
       
      FieldtypeRuntimeMarkup has access to $page (the current page being edited/viewed) and $pages. 
       
      A very simple example.
      return 'Hello'; Simple example.
      return $page->title; Simple example with markup.
      return '<h2>' . $page->title . '</h2>'; Another simple example with markup.
      $out = '<h1>hello '; $out .= $page->title; $out .= '</h1>'; return $out; A more advanced example.
      $p = $pages->get('/about-us/')->child('sort=random'); return '<p>' . $p->title . '</p>'; An even more complex example.
      $str =''; if($page->name == 'about-us') { $p = $page->children->last(); $str = "<h2><a href='{$p->url}'>{$p->title}</a></h2>"; } else { $str = "<h2><a href='{$page->url}'>{$page->title}</a></h2>"; } return $str; Rather than type your code directly in the Details tab of the field, it is highly recommended that you placed all your code in an external file and call that file using the core wireRenderFile() method. Taking this approach means you will be able to edit your code in your favourite text editor. It also means you will be able to type more text without having to scroll. Editing the file is also easier than editing the field. To use this approach, simply do:
      return wireRenderFile('name-of-file');// file will be in /site/templates/ If using ProcessWire 3.x, you will need to use namespace as follows:
      return ProcessWire\wireRenderFile('name-of-file'); How to access the value of RuntimeMarkup in the frontend (our field is called 'runtime_markup')
       
      Access the field on the current page (just like any other field)
      echo $page->runtime_markup; Access the field on another page
      echo $pages->get('/about-us/')->runtime_markup; Screenshots
       
      Backend
       

       

       
      Frontend
       

    • By kongondo
      Media Manager
       
      Released 31 March 2016
      https://processwireshop.pw/plugins/media-manager/
      Documentation 
      http://mediamanager.kongondo.com/
      As of 10 May 2019 ProcessWire versions earlier than 3.x are not supported
      *******************************************************   ORIGINAL POST   *******************************************************
      API Example (frontend; will be added to documentation site)
      Accessing and outputting the contents of the MediaManager field(s) in your template is quite simple. The fields are accessed like many other ProcessWire fields. The fields return an array of type MediaManagerArray that need to be looped to output each media within. Assuming you created a field of type MediaManager named 'media', you can loop through it for a given page as shown below.
        @note: Each MediaManager object has the following 5 basic properties:   DATABASE (saved properties) 1. id => pageID of the page where the media lives (hidden in admin and not important to know about) 2. type => integer denoting media type (1=audio; 2=document; 3=image [for variations this will be 3x, where x is the number of the variation of an original image]; 4=video)   RUNTIME 3. typeLabel => user friendly string denoting media type (audio, document, image, video) 4. media => a ProcessWire Image/File Object including all their properties (ext, filesizeStr, height, width, description, tags, filename, basename, etc.) 5. title => title of media (@note: this is the title of the page where the media lives; may or may not be the same as the name of the media file itself). This can be used as a user-friendly name for your media $media = $page->media;// returns a MediaManagerArray. Needs to be looped through foreach ($media as $m) { echo $m->id;// e.g. 1234 (hidden page in /admin/media-manager/media-parent/) echo $m->type;// e.g. 3 (a media of type image) OR 1 (a media of type audio) echo $m->typeLabel;// e.g. 'document' (i.e. type would be 2) echo $m->title;// e.g. 'My Nice Trip' (whose media file could be my-nice-trip.mp4) /* @note: - $m->media returns an object; either a ProcessWire Image (for image media) or File object (for audio, document and video media) - This means you have access to all the properties of that object, e.g. ext, tags, description, url, filename, basename, width, height, modified, created, filesize, filesizeStr, etc as well as associated methods, e.g. size() */ echo $m->media->tags; } // only output images foreach ($media as $m) { if($m->typeLabel =='image') { echo "<img src='" . $m->media->size(100,75)->url . "'><br>"; } } // There's also a toString() method so you can do: echo $page->media; /* All your media will be output wrapped in appropriate HTML tags, i.e.: audio: <audio></audio>; document: <a></a>; image: <img>; video: <video></video>; */  
      *******************************************************   ORIGINAL POST   *******************************************************
       
      The topic of a central media manager feature for ProcessWire has come up several times:
       
      https://processwire.com/talk/topic/4330-get-image-from-other-pages-via-images-field/
      https://processwire.com/talk/topic/4330-get-image-from-other-pages-via-images-field/?p=42578
      https://processwire.com/talk/topic/4330-get-image-from-other-pages-via-images-field/?p=42582
      https://processwire.com/talk/topic/425-file-manager/
      https://processwire.com/talk/topic/425-file-manager/?p=13802
      https://processwire.com/talk/topic/425-file-manager/?p=13861
      https://processwire.com/talk/topic/10763-asset-manager-asset-selector/
       
      More recently, regarding my Visual Page Selector module, I have been asked several times why the module does not have an in-built feature to upload images.
       
      There's two camps on the topic of a central media manager: those who like them (especially those coming in to PW from other CMSes) and those who don't like them (primarily because of the chaotic way some CMSes (dis)organise their media management) . I think that we can have our cake and eat it too! If done the right way, closely following the principles of and harnessing the power of ProcessWire, we can have a well-implemented, organised, feature-rich, site-wide media manager.
       
      Introducing Media Manager: (a commercial module)
       
      Alongside a number of modules I am currently working on (both free and commercial), I have been developing  a centralised Media Manager for ProcessWire. Before you cast the first stone, no, this is not going to be a one-large-media-bucket as in other CMS where it gets very messy very quickly . In the backend things are neatly stored away, yes, in pages. However, those are pages you will not see (just like repeater pages). Before anyone has a go at pages, remember a page is not that thing you see on the ProcessWire Tree (that's just its visual representation); A page is a record/row in the database    . For the end-user of Media Manager, all they will see is the 'familiar media bucket' to select their media from. As long as it works efficiently, I don't think they care about the wizardry behind the scenes  . 
       
      The module allows for the comprehensive management of several media types:
      Audio Video Images Documents Each media type will be handled by its own sub-module so the user can pick and install/choose the type of media management they want.
       
      Features include:
      Access controls Centralized uploads of media Bulk management of media: tag, delete, describe, replace, etc. Bulk upload: zip; scan, single Quick upload in page edit mode Usage stats across pages (maybe?) Etc.. Would love to hear your thoughts and any feature suggestions. I think there's enough demand for such a module. If not, please let me know so that I can instead focus on other things  , thanks.
       
      How other CMS do it

       
      The more efficient (PW) way of doing it

    • By Robin S
      I have had this module sitting in a 95% complete state for a while now and have finally made the push to get it out there. Thanks to @teppo for his Hanna Code Helper module which I referred to and borrowed from during development.
      http://modules.processwire.com/modules/hanna-code-dialog/
      https://github.com/Toutouwai/HannaCodeDialog
      HannaCodeDialog
      A module for ProcessWire CMS/CMF. Provides a number of enhancements for working with Hanna Code tags in CKEditor. The main enhancement is that Hanna tags in a CKEditor field may be double-clicked to edit their attributes using core ProcessWire inputfields in a modal dialog.
      Requires the Hanna Code module.
      Installation
      Install the HannaCodeDialog module using any of the normal methods.
      For any CKEditor field where you want the "Insert Hanna tag" dropdown menu to appear in the CKEditor toolbar, visit the field settings and add "HannaDropdown" to the "CKEditor Toolbar" settings field.
      Module configuration
      Visit the module configuration screen to set any of the following:
      Exclude prefix: Hanna tags named with this prefix will not appear in the CKEditor toolbar dropdown menu for Hanna tag insertion. Exclude Hanna tags: Hanna tags selected here will not appear in the CKEditor toolbar dropdown menu for Hanna tag insertion. Background colour of tag widgets: you can customise the background colour used for Hanna tags in CKEditor if you like. Dialog width: in pixels Dialog height: in pixels Features
      Insert tag from toolbar dropdown menu
      Place the cursor in the CKEditor window where you want to insert your Hanna tag, then select the tag from the "Insert Hanna tag" dropdown.

      Advanced: if you want to control which tags appear in the dropdown on particular pages or templates you can hook HannaCodeDialog::getDropdownTags. See the forum support thread for examples .
      Edit tag attributes in modal dialog
      Insert a tag using the dropdown or double-click an existing tag in the CKEditor window to edit the tag attributes in a modal dialog.

      Tags are widgets
      Hanna tags that have been inserted in a CKEditor window are "widgets" - they have a background colour for easy identification, are protected from accidental editing, and can be moved within the text by drag-and-drop.
      ![Hanna tag widget]
      Options for tag attributes may be defined
      You can define options for a tag attribute so that editors must choose an option rather than type text. This is useful for when only certain strings are valid for an attribute and also has the benefit of avoiding typos.
      Add a new attribute for the Hanna tag, named the same as the existing attribute you want to add options for, followed by "__options". The options themselves are defined as a string, using a pipe character as a delimiter between options. Example for an existing attribute named "vegetables":
      vegetables__options=Spinach|Pumpkin|Celery|Tomato|Brussels Sprout|Potato You can define a default for an attribute as normal. Use a pipe delimiter if defining multiple options as the default, for example:
      vegetables=Tomato|Potato Dynamic options
      Besides defining static options as above, you can use one Hanna tag to dynamically generate options for another. For instance, you could create a Hanna tag that generates options based on images that have been uploaded to the page, or the titles of children of the page.
      Your Hanna tag that generates the options should echo a string of options delimited by pipe characters (i.e. the same format as a static options string).
      You will probably want to name the Hanna tag that generates the options so that it starts with an underscore (or whatever prefix you have configured as the "exclude" prefix in the module config), to avoid it appearing as an insertable tag in the HannaCodeDialog dropdown menu.
      Example for an existing attribute named "image":
      image__options=[[_images_on_page]] And the code for the _images_on_page tag:
      <?php $image_names = array(); $image_fields = $page->fields->find('type=FieldtypeImage')->explode('name'); foreach($image_fields as $image_field) { $image_names = array_unique( array_merge($image_names, $page->$image_field->explode('name') ) ); } echo implode('|', $image_names); Advanced: define or manipulate options in a hook
      You can hook HannaCodeDialog::prepareOptions to define or manipulate options for a Hanna tag attribute. Your Hanna tag must include a someattribute__options attribute in order for the hook to fire. The prepareOptions method receives the following arguments that can be used in your hook:
      options_string Any existing string of options you have set for the attribute attribute_name The name of the attribute the options are for tag_name The name of the Hanna tag page The page being edited If you hook after HannaCodeDialog::prepareOptions then your hook should set $event->return to an array of option values, or an associative array in the form of $value => $label.
      Choice of inputfield for attribute
      You can choose the inputfield that is used for an attribute in the dialog.
      For text attributes the supported inputfields are text (this is the default inputfield for text attributes so it isn't necessary to specify it if you want it) and textarea. Note: any manual line breaks inside a textarea are removed because these will break the CKEditor tag widget.
      Inputfields that support the selection of a single option are select (this is the default inputfield for attributes with options so it isn't necessary to specify it if you want it) and radios.
      Inputfields that support the selection of multiple options are selectmultiple, asmselect and checkboxes.
      You can also specify a checkbox inputfield - this is not for attributes with defined options but will limit an attribute to an integer value of 1 or 0.
      The names of the inputfield types are case-insensitive.
      Example for an existing attribute named "vegetables":
      vegetables__type=asmselect Descriptions and notes for inputfields
      You can add a description or notes to an attribute and these will be displayed in the dialog.
      Example for an existing attribute named "vegetables":
      vegetables__description=Please select vegetables for your soup. vegetables__notes=Pumpkin and celery is a delicious combination. Notes
      When creating or editing a Hanna tag you can view a basic cheatsheet outlining the HannaCodeDialog features relating to attributes below the "Attributes" config inputfield.
      Troubleshooting
      HannaCodeDialog includes and automatically loads the third-party CKEditor plugins Line Utilities and Widget. If you have added these plugins to your CKEditor field already for some purpose and experience problems with HannaCodeDialog try deactivating those plugins from the CKEditor field settings.
×
×
  • Create New...