Jump to content
adrian

Tracy Debugger

Recommended Posts

@celfred - any chance this site is on a live server somewhere and you could give me access to figure out what is going on. 

PS Are you running the latest version of Tracy?

Share this post


Link to post
Share on other sites

@adrian Thanks for your reply. My site is at http://planetalert.tuxfamily.org . I have just installed TracyDenugger there. It doesn't appear but from what I've read in the settings, that's normal, everything is stored in log files. Ok, but how do I give you access to useful things (admin access?). Sorry if you feel like I'm messing things up and being a nuisance...

Actually, I've just tested 1 thing : forcing the DEV mode so I can see Tracy's bar. I saw the 'Processwire Debug Panel' and clicked on the 'Pages loaded' link, and it went to my 404 page like I said... I turned the setting back to DETECT. Feel free to tell me if you want me to do some things or to private message you some logs or whatever...

Edit : PM sent. Thank you so much.

Share this post


Link to post
Share on other sites

@celfred - I would need superuser access to the site to be able to test the issue of the pages loaded going to the 404 and also the issue of it appearing in the backend when not checked. Don't worry, you can trust me :) Obviously PM the login details.

Share this post


Link to post
Share on other sites

Thanks @adrian that's exactly what I was asking for.  I like the configuration as well.

I upgraded Tracy on two local sites, one site works correctly on the frontend and backend.  The other site doesn't show the toggle on the frontend, it works fine on the backend.  I'm not sure why yet.  I have tried uninstall/reinstalling the module.  I tried clearing the browser caches.  I tried refreshing the PW modules.  All I see on the frontend is the old Tracy debug bar.

Do you have any ideas what is causing this?

  • Like 1

Share this post


Link to post
Share on other sites
10 minutes ago, gmclelland said:

Thanks @adrian that's exactly what I was asking for.  I like the configuration as well.

I upgraded Tracy on two local sites, one site works correctly on the frontend and backend.  The other site doesn't show the toggle on the frontend, it works fine on the backend.  I'm not sure why yet.  I have tried uninstall/reinstalling the module.  I tried clearing the browser caches.  I tried refreshing the PW modules.  All I see on the frontend is the old Tracy debug bar.

Do you have any ideas what is causing this?

Are there any JS errors in the console for the frontend of the site where it isn't working? I am replacing the old close button with the hide button via JS so maybe there would be some clues there? Can you point me to the site?

 

Share this post


Link to post
Share on other sites

No js errors in the console.  Tried in different browsers as well.  I see the old 'X' button, I just don't see the new toggle button.  Sorry, the site is local.  I'll keep looking into it.

Home 2017-01-18 09-39-03.jpg

 

  • Like 1

Share this post


Link to post
Share on other sites

The site that is having a problem is using the Twig template engine using https://github.com/wanze/TemplateEngineFactory and https://github.com/wanze/TemplateEngineTwig.

I wonder if it is because the TracyDebugger module is using a hook to add the javascript?  I'm not very familiar with hooks, but maybe the hook doesn't run after Twig has compiled the markup?

  • Like 1

Share this post


Link to post
Share on other sites

Just as a follow-up in case people wonder, here's a copy of the message I sent to @adrian
 

Quote

 

I'm still struggling !!!

Here's what I have so far : In my head.inc, I had those lines (I can't remember why I needed them, really...)


$whitelist = array('127.0.0.1', 'localhost');
if(!in_array($_SERVER['REMOTE_ADDR'], $whitelist)){
   // Remote server
   echo "<base href='/index.html'>";
 } else {
   // Localhost
   echo "<base href='/PlanetAlert/index.html'>";
 }

 I commented them out on localhost and Tracy works as expected ! Thanks for your help !

Now I'll check later if I can comment these lines out on live site ;) And I'm gonna dig this Teams page but that will be for my other post on 'Optimisation' :)

Thanks again !

 

 

  • Like 1

Share this post


Link to post
Share on other sites

Ok, on line 294 of TracyDebugger.module, I changed it to

$this->addHookAfter('Page::render', $this, 'addCustomStuff', array('priority'=>'100.7'));

After I did this, I started seeing the toggle link on the frontend.

The templateEngineFactory module (Page::render() TemplateEngineFactory::hookRender()) had a priority of 100.5.  TracyDebugger had a priority of 100.4, so it ran too early.

What do you think is the best way to fix this?

 

  • Like 1

Share this post


Link to post
Share on other sites

@gmclelland - thanks for helping to track that down!

I think that 100.5 priority in TemplateEngineFactory is being set automatically. I am honestly not sure the best way to approach fixing this. The most guaranteed would probably be if I manually set it to say 1000, to make sure it is after any other hooks that might also manually set the priority to a high value. I guess I'll do that for now. There are actually a few Page::render hooks used in Tracy, so I will take care of those as well because I feel like TemplateEngineFactory will be breaking those as well.

Thanks again!

Share this post


Link to post
Share on other sites

@gmclelland and everyone.

Latest version takes care of the hook priority issue and adds a new feature to the new hide/show toggle button.

Now if you have it hidden and it detects an error it will force it to display. Once you fix the error, it will go back to being hidden again. I think this is a nice compromise for those who don't like having the debug bar visible all the time, but don't want to miss any reported notices/warnings.

Please let me know if you notice any problems with this change.

  • Like 3

Share this post


Link to post
Share on other sites

@adrian - Thanks for adding that new feature.  I just tested the new version and noticed a few of issues.

1. I don't think the "Hide debug bar by default" setting is working for me anymore.  I swear it was working before.  Now, the debug bar always shows expanded when enabled on the frontend or backend.

2. Maybe add checkboxes for a "Hide debug bar by default on the frontend" and "Hide debug bar by default on the backend" settings?

3. I don't think the padding got applied to the toggle when the bar is in a collapsed state when viewed on the backend.  I'm using the default admin theme.  You can see this by toggling the bar.  The height of the toggle button doesn't match the height of the debug bar.  It looks fine on the frontend though.

Share this post


Link to post
Share on other sites

Nevermind about  #1. I see that works properly.  I was assuming that it would be collapsed by default on every page load.  The actual behavior is that it remembers if it was opened or closed and stays that way between page loads.

  • Like 1

Share this post


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

1. I don't think the "Hide debug bar by default" setting is working for me anymore.  I swear it was working before.  Now, the debug bar always shows expanded when enabled on the frontend or backend.

Once you have clicked to show it, a cookie is set which overrides the config setting. Or is this because there are errors in the errors panel, which as I mentioned now forces it to display, which I think is a good idea, but can revisit/make configurable if you needs don't like it.
 

2 minutes ago, gmclelland said:

2. Maybe add checkboxes for a "Hide debug bar by default on the frontend" and "Hide debug bar by default on the backend" settings?

I know I already have a lot of settings, but I feel like this might be going a little too far :) especially given how easy it is to toggle.
 

4 minutes ago, gmclelland said:

3. I don't think the padding got applied to the toggle when the bar is in a collapsed state when viewed on the backend.  I'm using the default admin theme.  You can see this by toggling the bar.  The height of the toggle button doesn't match the height of the debug bar.  It looks fine on the frontend though.

It looks the same to me both front and backend. Perhaps you have extra padding on the frontend due to some css cascading down? Could you maybe post some comparison screenshots and/or debug the css to see what might be conflicting.

Thanks.

Share this post


Link to post
Share on other sites

It's a subtle difference that can only be seen when toggling back and forth.

Here is the frontend

frontend.gif

 

Here is the backend

backend.gif

  • Like 1

Share this post


Link to post
Share on other sites
Now if you have it hidden and it detects an error it will force it to display. 

How about extending it to bd() calls too?

Share this post


Link to post
Share on other sites
3 hours ago, tpr said:

Now if you have it hidden and it detects an error it will force it to display. 

How about extending it to bd() calls too?

Not sure about this - I like your thinking, but then where do I stop? Do I extend it even further to display if there is a new PW or Logs panel item? What about a new Mail panel or Page recorder entry?

I think perhaps that manually triggered things shouldn't automatically unhide the bar because you know you've added the call so you will be looking for an entry on the bar. If anything I think maybe the logs panels should maybe trigger display of the bar if they are error related entries.

As always though I am open to feedback if others think this change would be good.

Share this post


Link to post
Share on other sites

To fix the toggle button height and width jumping, I had to add the following to #show-button:

box-sizing: border-box;
line-height: normal;
padding: 4px 15px 2px 6px !important;
width: 16px !important;

So all together it looks like this:

#show-button {
    bottom: 0;
    right: 0;
    z-index: 99999;
    position: fixed;
    width: 16px !important;
    margin: 0 !important;
    padding: 4px 15px 2px 6px !important;
    background: #FFFFFF !important;
    border: 1px solid #DDDDDD !important;
    font-size: 12px !important;
    cursor: pointer;
    box-sizing: border-box;
    line-height: normal;
}

Works in the default and Reno admin themes and my frontend theme.  Hope that helps

Here is the pull request https://github.com/adrianbj/TracyDebugger/pull/9

  • Like 1

Share this post


Link to post
Share on other sites
1 hour ago, adrian said:

Not sure about this - I like your thinking, but then where do I stop? 

It's up to you :) I'm fine with the expanded bar too, just thought this could save some clicks.

Share this post


Link to post
Share on other sites

New Captain Hook panel just added!

Features:

  1. The hooks are parsed directly from the files in your PW installation, so they will always be up to date.
  2. They are cached, but will be updated whenever you upgrade your PW version.
  3. If you have your Editor Protocol Handler properly configured for Tracy, clicking on the Line Number will open to the method in your code editor.

This panel uses @owzim's Captain Hook generator: https://github.com/owzim/PWCaptainHookCLI

Please let me know if you have any problems or suggestions.

Screen Shot 2017-01-24 at 10.43.45 PM.png

  • Like 8

Share this post


Link to post
Share on other sites

I'm seeing an error in the new Captain Hook panel on Windows - I think it's the path slashes issue.

ErrorException: file_get_contents(D:/Websites/__www/1testing/wire/): failed to open stream: No such file or directory in D:\Websites\__www\1testing\site\assets\cache\FileCompiler\site\modules\TracyDebugger\CaptainHook\classes\CaptainHookSearch.php:44

Dumping $filenamesArray in CaptainHookSearch::getHooks() shows paths like...

"D:/Websites/__www/1testing/wire/"
"D:/Websites/__www/1testing/wire\config.php"
"D:/Websites/__www/1testing/wire\core\admin.php"
"D:/Websites/__www/1testing/wire\core\boot.php"
...

Edit: actually, it might be the first item in the array that's the problem: "D:/Websites/__www/1testing/wire/". Seems like this shouldn't be in there seeing as it's a directory and and not a .php or .module file.

  • Like 1

Share this post


Link to post
Share on other sites

Thanks - also an error here:

ErrorException: is_file(): open_basedir restriction in effect. File(classes/CaptainHookSearch.php)

 

Share this post


Link to post
Share on other sites

Problem seems to be here:

$paths = array($root);

Might be misunderstanding something but don't think the root directory is wanted in that array.

  • 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 ukyo
      Mystique Module for ProcessWire CMS/CMF
      Github repo : https://github.com/trk/Mystique
      Mystique module allow you to create dynamic fields and store dynamic fields data on database by using a config file.
      Requirements
      ProcessWire 3.0 or newer PHP 7.0 or newer FieldtypeMystique InputfieldMystique Installation
      Install the module from the modules directory:
      Via Composer:
      composer require trk/mystique Via git clone:
      cd your-processwire-project-folder/ cd site/modules/ git clone https://github.com/trk/Mystique.git Module in live reaction with your Mystique config file
      This mean if you remove a field from your config file, field will be removed from edit screen. As you see on youtube video.
      Using Mystique with your module or use different configs path, autoload need to be true for modules
      Default configs path is site/templates/configs/, and your config file name need to start with Mystique. and need to end with .php extension.
      // Add your custom path inside ready or init function, didn't tested outside Mystique::add('your-configs-path'); All config files need to return a php array like examples.
      Same as ProcessWire Inputfield Api, only difference is set and showIf usage
      <?php namespace ProcessWire; /** * Resource : testing-mystique */ return [ 'title' => __('Testing Mystique'), 'fields' => [ 'text_field' => [ 'label' => __('You can use short named types'), 'description' => __('In file showIf working like example'), 'notes' => __('Also you can use $input->set() method'), 'type' => 'text', 'showIf' => [ 'another_text' => "=''" ], 'set' => [ 'showCount' => InputfieldText::showCountChars, 'maxlength' => 255 ], 'attr' => [ 'attr-foo' => 'bar', 'attr-bar' => 'foo' ] ], 'another_text' => [ 'label' => __('Another text field (default type is text)') ] ] ]; Example:
      site/templates/configs/Mystique.seo-fields.php <?php namespace ProcessWire; /** * Resource : seo-fields */ return [ 'title' => __('Seo fields'), 'fields' => [ 'window_title' => [ 'label' => __('Window title'), 'type' => Mystique::TEXT, // or InputfieldText 'useLanguages' => true, 'attr' => [ 'placeholder' => __('Enter a window title') ] ], 'navigation_title' => [ 'label' => __('Navigation title'), 'type' => Mystique::TEXT, // or InputfieldText 'useLanguages' => true, 'showIf' => [ 'window_title' => "!=''" ], 'attr' => [ 'placeholder' => __('Enter a navigation title') ] ], 'description' => [ 'label' => __('Description for search engines'), 'type' => Mystique::TEXTAREA, 'useLanguages' => true ], 'page_tpye' => [ 'label' => __('Type'), 'type' => Mystique::SELECT, 'options' => [ 'basic' => __('Basic page'), 'gallery' => __('Gallery'), 'blog' => __('Blog') ] ], 'show_on_nav' => [ 'label' => __('Display this page on navigation'), 'type' => Mystique::CHECKBOX ] ] ]; Searching data on Mystique field is limited. Because, Mystique saving data to database in json format. When you make search for Mystique field, operator not important. Operator will be changed with %= operator.
      Search example
      $navigationPages = pages()->find('my_mystique_field.show_on_nav=1'); $navigationPages = pages()->find('my_mystique_field.page_tpye=gallery');
    • By Robin S
      File Info
      A textformatter module for ProcessWire. The module can add information to local Pagefile links in two ways:
      As extra markup before, within or after the link As data attributes on the link (handy if you want to use a Javascript tooltip library, for instance) Screenshots
      Module config

      Example of output

      Installation
      Install the File Info module.
      Add the textformatter to one or more CKEditor fields.
      Configuration
      Add markup action (and general)
      Select "Add markup to links" Select the Pagefile attributes that will be retrieved. The attribute "filesizeStrCustom" is similar to the core "filesizeStr" attribute but allows for setting a custom number of decimal places. If you select the "modified" or "created" attributes then you can define a date format for the value. Enter a class string to add to the links if needed. Define the markup that will be added to the links. Surround Pagefile attribute names in {brackets}. Attributes must be selected in the "Pagefile attributes" section in order to be available in the added markup. If you want include a space character at the start or end of the markup then you'll need >= PW 3.0.128. Select where the markup should be added: prepended or appended within the link, before the link, or after the link. Add data attributes action
      Select "Add data attributes to links" Select the Pagefile attributes that will be retrieved. These attributes will be added to the file links as data attributes. Attributes with camelcase names will be converted to data attribute names that are all lowercase, i.e. filesizeStrCustom becomes data-filesizestrcustom. Hook
      If you want to customise or add to the attributes that are retrieved from the Pagefile you can hook TextformatterFileInfo::getFileAttributes(). For example:
      $wire->addHookAfter('TextformatterFileInfo::getFileAttributes', function(HookEvent $event) { $pagefile = $event->arguments(0); $page = $event->arguments(1); $field = $event->arguments(2); $attributes = $event->return; // Add a new attribute $attributes['sizeNote'] = $pagefile->filesize > 10000000 ? 'This file is pretty big' : 'This file is not so big'; $event->return = $attributes; });  
      https://github.com/Toutouwai/TextformatterFileInfo
      https://modules.processwire.com/modules/textformatter-file-info/
    • By Robin S
      Access By Query String
      Grant/deny access to pages according to query string.
      Allows visitors to view protected pages by accessing the page via a special URL containing an "access" GET variable. This allows you to provide a link to selected individuals while keeping the page(s) non-viewable to the public and search engines. The recipients of the link do not need to log in so it's very convenient for them.
      The view protection does not provide a high level of security so should only be used for non-critical scenarios. The purpose of the module was to prevent new websites being publicly accessible before they are officially launched, hence the default message in the module config. But it could be used for selected pages on existing websites also.
      Once a visitor has successfully accessed a protected page via the GET variable then they can view any other page protected by the same access rule without needing the GET variable for that browsing session.
      Superusers are not affected by the module.
      Usage
      Install the Access By Query String module.
      Define access rules in the format [GET variable]??[selector], one per line.
      As an example the rule...
      rumpelstiltskin??template=skills, title~=gold ...means that any pages using the "skills" template with the word "gold" in the title will not be viewable unless it is accessed with ?access=rumpelstiltskin in the URL. So you could provide a view link like https://domain.com/skills/spin-straw-into-gold/?access=rumpelstiltskin to selected individuals.
      Or you could limit view access to the whole frontend with a rule like...
      4fU4ns7ZWXar??template!=admin You can choose what happens when a protected page is visited without the required GET variable:
      Replace the rendered markup Throw a 404 exception If replacing the rendered markup you can define a meta title and message to be shown. Or if you want to use more advanced markup you can hook AccessByQueryString::replacementMarkup().
      $wire->addHookAfter('AccessByQueryString::replacementMarkup', function(HookEvent $event) { // Some info in hook arguments if needed... // The page that the visitor is trying to access $page = $event->arguments(0); // An array of access keys that apply to the page $access_keys = $event->arguments(1); // The title $title = $event->arguments(2); // The message $message = $event->arguments(3); // Return some markup $event->return = 'Your markup'; }); Screenshot

       
      https://github.com/Toutouwai/AccessByQueryString
      https://modules.processwire.com/modules/access-by-query-string/
    • By horst
      Wire Mail SMTP

      An extension to the (new) WireMail base class that uses SMTP-transport

      This module integrates EmailMessage, SMTP and SASL php-libraries from Manuel Lemos into ProcessWire. I use this continously evolved libraries for about 10 years now and there was never a reason or occasion not to do so. I use it nearly every day in my office for automated composing and sending personalized messages with attachments, requests for Disposition Notifications, etc. Also I have used it for sending personalized Bulkmails many times.

      The WireMailSmtp module extends the new email-related WireMail base class introduced in ProcessWire 2.4.1 (while this writing, the dev-branch only).
       
      Here are Ryans announcement.



      Current Version 0.3.1
      get it from the Modules Directory Install and Configure

      Download the module into your site/modules/ directory and install it.

      In the config page you fill in settings for the SMTP server and optionaly the (default) sender, like email address, name and signature.
      You can test the smtp settings directly there. If it says "SUCCESS! SMTP settings appear to work correctly." you are ready to start using it in templates, modules or bootstrap scripts.


      Usage Examples
      The simplest way to use it:
      $numSent = wireMail($to, $from, $subject, $textBody); $numSent = wireMail($to, '', $subject, $textBody); // or with a default sender emailaddress on config page This will send a plain text message to each recipient.
       
      You may also use the object oriented style:
      $mail = wireMail(); // calling an empty wireMail() returns a wireMail object $mail->to($toEmail, $toName); $mail->from = $yourEmailaddress; // if you don't have set a default sender in config // or if you want to override that $mail->subject($subject); $mail->body($textBody); $numSent = $mail->send(); Or chained, like everywhere in ProcessWire:
      $mail = wireMail(); $numSent = $mail->to($toEmail)->subject($subject)->body($textBody)->send(); Additionaly to the basics there are more options available with WireMailSmtp. The main difference compared to the WireMail BaseClass is the sendSingle option. With it you can set only one To-Recipient but additional CC-Recipients.
      $mail = wireMail(); $mail->sendSingle(true)->to($toEmail, $toName)->cc(array('person1@example.com', 'person2@example.com', 'person3@example.com')); $numSent = $mail->subject($subject)->body($textBody)->send(); The same as function call with options array:
      $options = array( 'sendSingle' => true, 'cc' => array('person1@example.com', 'person2@example.com', 'person3@example.com') ); $numSent = wireMail($to, '', $subject, $textBody, $options); There are methods to your disposal to check if you have the right WireMail-Class and if the SMTP-settings are working:
      $mail = wireMail(); if($mail->className != 'WireMailSmtp') { // Uups, wrong WireMail-Class: do something to inform the user and quit echo "<p>Couldn't get the right WireMail-Module (WireMailSmtp). found: {$mail->className}</p>"; return; } if(!$mail->testConnection()) { // Connection not working: echo "<p>Couldn't connect to the SMTP server. Please check the {$mail->className} modules config settings!</p>"; return; } Following are a ...


      List of all options and features


      testConnection () - returns true on success, false on failures


      sendSingle ( true | false ) - default is false

      sendBulk ( true | false ) - default is false, Set this to true if you have lots of recipients (50+)


      to ($recipients) - one emailaddress or array with multiple emailaddresses

      cc ($recipients) - only available with mode sendSingle, one emailaddress or array with multiple emailaddresses

      bcc ($recipients) - one emailaddress or array with multiple emailaddresses

       
      from = 'person@example.com' - emailaddress, can be set in module config (called Sender Emailaddress) but it can be overwritten here

      fromName = 'Name Surname' - optional, can be set in module config (called Sender Name) but it can be overwritten here


      priority (3) - 1 = Highest | 2 = High | 3 = Normal | 4 = Low | 5 = Lowest

      dispositionNotification () or notification () - request a Disposition Notification


      subject ($subject) - subject of the message

      body ($textBody) - use this one alone to create and send plainText emailmessages

      bodyHTML ($htmlBody) - use this to create a Multipart Alternative Emailmessage (containing a HTML-Part and a Plaintext-Part as fallback)

      addSignature ( true | false ) - the default-behave is selectable in config screen, this can be overridden here
      (only available if a signature is defined in the config screen)

      attachment ($filename, $alternativeBasename = "") - add attachment file, optionally alternative basename


      send () - send the message(s) and return number of successful sent messages


      getResult () - returns a dump (array) with all recipients (to, cc, bcc) and settings you have selected with the message, the message subject and body, and lists of successfull addresses and failed addresses,


      logActivity ($logmessage) - you may log success if you want

      logError ($logmessage) - you may log warnings, too. - Errors are logged automaticaly
       
       
      useSentLog (true | false) - intended for usage with e.g. third party newsletter modules - tells the send() method to make usage of the sentLog-methods - the following three sentLog methods are hookable, e.g. if you don't want log into files you may provide your own storage, or add additional functionality here

      sentLogReset ()  - starts a new LogSession - Best usage would be interactively once when setting up a new Newsletter

      sentLogGet ()  - is called automaticly within the send() method - returns an array containing all previously used emailaddresses

      sentLogAdd ($emailaddress)  - is called automaticly within the send() method
       
      Changelog: https://github.com/horst-n/WireMailSmtp/blob/master/CHANGELOG.md
       
      LATEST UPDATE:
       
    • By David Karich
      ProcessWire InputfieldRepeaterMatrixDuplicate
      Thanks to the great ProModule "RepeaterMatrix" I have the possibility to create complex repeater items. With it I have created a quite powerful page builder. Many different content modules, with many more possible design options. The RepeaterMatrix module supports the cloning of items, but only within the same page. Now I often have the case that very design-intensive pages and items are created. If you want to use a content module on a different page (e.g. in the same design), you have to rebuild each item manually every time.
      This module extends the commercial ProModule "RepeaterMatrix" by the function to duplicate repeater items from one page to another page. The condition is that the target field is the same matrix field from which the item is duplicated. This module is currently understood as proof of concept. There are a few limitations that need to be considered. The intention of the module is that this functionality is integrated into the core of RepeaterMatrix and does not require an extra module.
      Check out the screencast
      What the module can do
      Duplicate a repeater item from one page to another No matter how complex the item is Full support for file and image fields Multilingual support Support of Min and Max settings Live synchronization of clipboard between multiple browser tabs. Copy an item and simply switch the browser tab to the target page and you will immediately see the past button Support of multiple RepeaterMatrix fields on one page Configurable which roles and fields are excluded Duplicated items are automatically pasted to the end of the target field and set to hidden status so that changes are not directly published Automatic clipboard update when other items are picked Automatically removes old clipboard data if it is not pasted within 6 hours Delete clipboard itself by clicking the selected item again Benefit: unbelievably fast workflow and content replication What the module can't do
      Before an item can be duplicated in its current version, the source page must be saved. This means that if you make changes to an item and copy this, the old saved state will be duplicated Dynamic loading is currently not possible. Means no AJAX. When pasting, the target page is saved completely No support for nested repeater items. Currently only first level items can be duplicated. Means a repeater field in a repeater field cannot be duplicated. Workaround: simply duplicate the parent item Dynamic reloading and adding of repeater items cannot be registered. Several interfaces and events from the core are missing. The initialization occurs only once after the page load event Changelog
      1.0.4
      Bug fix: Various bug fixes and improvements in live synchronization Bug fix: Items are no longer inserted when the normal save button is clicked. Only when the past button is explicitly clicked Feature: Support of multiple repeater fields in one page Feature: Support of repeater Min/Max settings Feature: Configurable roles and fields Enhancement: Improved clipboard management Enhancement: Documentation improvement Enhancement: Corrected few typos #1 1.0.3
      Feature: Live synchronization Enhancement: Load the module only in the backend Enhancement: Documentation improvement 1.0.2
      Bug fix: Various bug fixes and improvements in JS functions Enhancement: Documentation improvement Enhancement: Corrected few typos 1.0.1
      Bug fix: Various bug fixes and improvements in the duplication process 1.0.0
      Initial release Support this module
      If this module is useful for you, I am very thankful for your small donation: Donate 5,- Euro (via PayPal – or an amount of your choice. Thank you!)
      Download this module
      > Github: https://github.com/FlipZoomMedia/InputfieldRepeaterMatrixDuplicate
      > PW module directory: – soon –
×
×
  • Create New...