Jump to content

Module: RuntimeMarkup Fieldtype & Inputfield


kongondo

Recommended Posts

@Juergen I have used this module with ProcessWire's translation capabilities with no problems!

And actually, forgot to mention that on my previous post. Once upon a time, a client wanted to control the contrast of their b&w converted image, so with the help of @horst 's PIM 2 module and RuntimeMarkup I was able to quickly setup a "thumb preview and edit" button. All buttons and text were in spanish and english.

Screen Shot 2017-02-10 at 6.31.19 PM.png

  • Like 6
Link to comment
Share on other sites

  • 1 month later...
2 hours ago, elabx said:

Is there a reason ProcessWire would be stripping a <form> html element when embedding code through this module?

i guess the browser strips your form because it is inside the processwire form that contains all the inputfields and a form inside another form is not valid html. the inspector shows you the code after browser and javascript manipulations. if you view the raw sourcecode you maybe see your form element.

http://stackoverflow.com/questions/555928/is-it-valid-to-have-a-html-form-inside-another-html-form

  • Like 2
Link to comment
Share on other sites

hi @kongondo

what do you think of adding a feature that the field loads files with the same filename automatically when they exist?

for example a field "runtime_demo" would load /somefolder/runtime_demo.php and /somefolder/runtime_demo.js

i do it manually right now. for sure no problem but i think that would help to keep everything clear if you are using custom markup a lot :)

 

edit: is there a reason why my file is loaded 3 times when using wirerenderfile? if i only put

bd('test!');

into the file, then i see it 3 times in the tracy log. i setup a datatable with my module and loaded the code in the runtime markup field. i had my columns 3 times. i fixed it with an if-statement, but still i would be interested why the file is called 3 times...

Link to comment
Share on other sites

  • 4 weeks later...
12 hours ago, Nukro said:

Very Nice Module you have created here! I have a question, would it be possible to use this module inside the Formbuilder somehow. Is it even supported by the Formbuilder?

Glad the module is of use to you. Unfortunately, I have never had the need to use Formbuilder. Maybe you could try and let us know? Thanks.

Link to comment
Share on other sites

On 27.3.2017 at 11:08 AM, bernhard said:

hi @kongondo

what do you think of adding a feature that the field loads files with the same filename automatically when they exist?

for example a field "runtime_demo" would load /somefolder/runtime_demo.php and /somefolder/runtime_demo.js

i do it manually right now. for sure no problem but i think that would help to keep everything clear if you are using custom markup a lot :)

would you mind adding my suggested features to your module?

sorry for not making a PR, but you can just replace your render method with this one:

    /**
     * Render the entire markup returned from FieldtypeRuntimeMarkup
     *
     */
    public function ___render() {

        //so that $page and $pages are locally scoped to the eval
        $process = $this->wire('process'); 
        if($process && $process->className() == 'ProcessPageEdit') $page = $process->getPage();

        $pages = $this->wire('pages');

        // render files that are related to this field
        $root = rtrim($this->wire->config->paths->root,'/');
        $file = '/site/modules/FieldtypeRuntimeMarkup/fields/' . $this->name;
        if(is_file($root.$file.'.php')) {
            // we found a file in the modules /fields folder, so render it
            $str = wireRenderFile($root.$file);
        }
        else {
            // no early reaturn because we load assets later
            if(!$this->runtimeFields) $str = '';
            else $str = eval($this->runtimeFields);
        }

        // load assets related to this field
        if(is_file($root.$file.'.js')) $this->wire->config->scripts->add($file.'.js');
        if(is_file($root.$file.'.css')) $this->wire->config->styles->add($file.'.css');

        //since we are dealing with custom PHP code but also want to make sure that only markup is returned
        //if eval() returns anything other than a string or an integer, we throw an error (e.g. if an object or array is returned)
        if (is_string($str) || is_int($str)) return $str;
        else return $this->error($this->_('Only strings and integers should be returned by your custom code! Check if your code is valid.'));
    }

this will render all files inside the folder

/site/modules/FieldtypeRuntimeMarkup/
- your_field_name.php | .css | .js

  • Like 2
Link to comment
Share on other sites

On 3.7.2017 at 10:44 PM, kongondo said:

Glad the module is of use to you. Unfortunately, I have never had the need to use Formbuilder. Maybe you could try and let us know? Thanks.

I had tried and it looks like it's not supported. There is no Detail Tab / Textarea or something where you can add the PHP Code. I came up with a workaround using InputfieldMarkup and Hanna Code Tags. But still, thank you for your Support @kongondo.

Greetings Nukro

Link to comment
Share on other sites

  • 2 weeks later...

hi @kongondo 

did you think about my suggested new render method?

another thing that would be good imho is to mention in the docs / in the first posting that you can do this

return ProcessWire\wireRenderFile('fields/myfieldsphpfile.php', ['page' => $page]);

To have the currently edited page available in your file. It's very basic, but might help some beginners.

I would also suggest to update my render-method passing the $page and $pages variables to the renderfile:

// change this
$str = wireRenderFile($root.$file);

// to that
$str = wireRenderFile($root.$file, [
  'page' => $page,
  'pages' => $pages,
]);

what do you think?

  • Like 4
Link to comment
Share on other sites

Update: Runtime Markup Version 0.0.3.

Changelog

  1. Added support to render PHP, JavaScript and CSS files Thanks to @bernhard for the ideas.

Please note:

  • Please read the notes that accompany the field settings.
  • For PHP, you can choose to render files (recommended) vs paste code.
  • JavaScript and CSS work with either PHP rendering method (above). These are optional to use.
  • For each of the 3 file types above, if you only have one file and this is named identical to your field, you can select an option to have those rendered/added. For example, if you have a RuntimeMarkup field called 'my_field', you can have a 'my_field.php', 'my_field.js' and 'my_field.css' automatically rendered/added.
  • However, if you want to render multiple files and/or these are named differently, select the option that indicates the files have different names. In that case, enter comma-separated file names. For example, for CSS: my_css, styles/my-other-css-file. Using this option, you can include external JavaScript libraries for use on your page if you fancied it.
  • The above can be mixed and matched, e.g. PHP file could have name identical to field but JavaScript are multiple files with different names and CSS multiple file names, one of which could share a name with your field.
  • All files must descend from either of the root paths /site/templates/ or /site/modules/. It is OK for files to be in sub-folders, as long as those descend from one of these root paths. There is a setting to indicate root path. Only one root path can be used at a time, i.e. it applies to all file types.
  • .php, .js and .css extensions are assumed and do not need to be specified with the file names. PHP files such as .inc will need to be input as such, e.g. my_code.inc,includes/my-more-code.tpl.
  • Errors will be shown if files not found.
  • In your rendered PHP file, you have access to $page and $pages. This means you do not need to get the page being edited first to use it as the current page.
  • For frontend, only pasted PHP code option is supported. My take is that this module is primarily used for the backend. Use of the render files option is geared for creating complex and/or more flexible backend apps as opposed to frontend usage. I have no intention of changing this behaviour.

Currently available on dev branch only. Please test and let me know (with Listers, etc as well, thanks).

Screenshots

Backend Settings

rm-backend-settings-1-version-003.thumb.png.3abb7b941574a1f0f844cacf27da779f.pngrm-backend-settings-2-version-003.thumb.png.1b3a213250984b10d7964e65c8e0408d.pngrm-backend-settings-3-version-003.thumb.png.27c35c5ce4b4b68c1946d1623079de36.png

Backend Output

rm-backend-output-version-003.thumb.png.9b16110fb57039545acf3134cd8079d1.png

Edited by kongondo
more info
  • Like 3
Link to comment
Share on other sites

hi @kongondo 

I just tried the dev version and have 2 questions:

  • what is the reason for specifying the root path as /templates or /modules ? Why not a folder inside the RuntimeMarkup's module folder? like /FieldtypeRuntimeMarkup/fields ? Ok, i can specify an alternate filename, but imho that is an unnecessary step and it would be preferable to have this at least as an option. I try to keep the templates' and modules' root folders as clean as possible... edit: of course that would not be a good idea because module updates would wipe all code files in this folder!
  • Second thing that i find more annoying than helping is the js and css file include warnings / settings. Why do i have to select if there is a js/css file present? Why does it not include a js/css file automatically if one is present. Imagine you are working on a runtime field and want to do some minor css changes. you are in your IDE and you would just have to create a new css file with the name of your field. But as it is now, i would also have to change the field's settings. Thats some more extra clicks that i don't understand why they are necessary if my proposed render method did not have this drawbacks.

maybe there is a reason for that and i would be happy to hear it :)

thanks for bringing my ideas into your module though!

Link to comment
Share on other sites

7 hours ago, bernhard said:

what is the reason for specifying the root path as /templates or /modules ?

Added security...similar to wireRenderFile().

7 hours ago, bernhard said:

Why not a folder inside the RuntimeMarkup's module folder? like /FieldtypeRuntimeMarkup/fields ? Ok, i can specify an alternate filename

Yes you can specify a filename :). FieldtypeRuntimeMarkup/fields/my-file. 

7 hours ago, bernhard said:

it would be preferable to have this at least as an option.

OK. I'll add that as a third option (or as the first option).

 

7 hours ago, bernhard said:

I try to keep the templates' and modules' root folders as clean as possible

Sure. But some people may prefer to create include folders in /site/templates/ and /site/modules/ that are shared across the site. Adding a third option above should cater for both worlds.

7 hours ago, bernhard said:

Why do i have to select if there is a js/css file present?

We can't assume everyone will want to include a JS/CSS file :).

 

7 hours ago, bernhard said:

Why does it not include a js/css file automatically if one is present.

I don't like automating things TBH. I prefer for users to expressly declare a choice.

 

7 hours ago, bernhard said:

Imagine you are working on a runtime field and want to do some minor css changes. you are in your IDE and you would just have to create a new css file with the name of your field.

OK. Imagine you are working on a runtime field and want to do some 'minor' JS changes. You are in your IDE and you would just have to create a new js file with the name of your field. But then you have to leave or you forgot to fully test your changes with other Inputfields present on the page and you lock up the whole page edit (yes, that's what JS will do...) ;).  Or...you or a colleague renamed your field and forgot to rename your files..:P.

 

7 hours ago, bernhard said:

But as it is now, i would also have to change the field's settings. Thats some more extra clicks that i don't understand why they are necessary if my proposed render method did not have this drawbacks.

Please see above point. IMO, this is a minor inconvenience compared to the damage automation could cause. OK, maybe I exaggerate but I am not convinced automation is the best approach in this particular case. The field settings are just a click away. Yes, I could include an option to suppress errors but that's no good either. Errors need to be seen so that they can be rectified. 

 

7 hours ago, bernhard said:

thanks for bringing my ideas into your module though!

^-^

Edited by kongondo
  • Like 2
Link to comment
Share on other sites

thanks for your reply!

I think your answers are totally out of context some times. For example specifying a root path is not added security compared to my suggestion of having a fields folder inside the runtime markup module. but this point will be fixed when we have another option, so thank you for taking that into account :)

Regarding the automatic include of js+css files: I really disagree about that. Your point about breaking the edit screen has nothing to do with the way the file is included! I would also break the edit screen when i include a broken JS file that is specified in the field's settings. IMHO braking up all into 3 config fields adds the possibility of errors because you can easily have typos etc.

if you have your root path for the field (wherever it is, i understand your point about modules and templates) and you have a my_field.php file there. its much more secure and error-unlikely to just put a new file in the same folder (having it grouped in the filetree because of the same filename beginnings) and have that load automatically when present. i don't think that the error message is necessary or helpful for the USER of the field, because if something does not work as expected, you can easily do an alert('working') or the like. I think those error messages only help you as a DEV of the module for finding bugs while writing all the include paths etc.

OK... given that you set your field to include a file in a custom directory it may help to get an error (for example to find typos)... i just didn't think of that too much because i only had one folder and that was really fool-proof to place a file there.

considering the fact that this could be helpful sometimes and that imho it is NOT more unsecure to include the js+css automatically if present i would really like to see that as a third option too :) 

thank you for your time - please don't be mad about me picking on so little things... that's just the proof that i'm using your module a lot those days ;)

Link to comment
Share on other sites

4 minutes ago, bernhard said:

For example specifying a root path is not added security compared to my suggestion of having a fields folder inside the runtime markup module.

Yes, you are right. Regarding security, I was responding to the issue about root paths in general, but now I realise what you were really after is having the field's folder as a default. Anyway, this is resolved with having the third option I mentioned.

 

5 minutes ago, bernhard said:

i don't think that the error message is necessary or helpful for the USER of the field, because if something does not work as expected, you can easily do an alert('working') or the like. I think those error messages only help you as a DEV of the module for finding bugs while writing all the include paths etc.

Yes, the error messages are for the dev. Maybe I misunderstand; did you have a suggestion regarding error messages?

 

9 minutes ago, bernhard said:

considering the fact that this could be helpful sometimes and that imho it is NOT more unsecure to include the js+css automatically if present i would really like to see that as a third option too :) 

You already have this option :). OK, two options, one each for JS and CSS. So, rather than having one option "JavaScript and CSS included automatically", we have split that into two for JS and CSS respectively. The second options under JS and CSS "JavaScript/CSS file has identical name to this field".  That will do what you are after, but with the errors of course, if there is no file present. I think that's a good reminder about missing files. Maybe we can add an option to suppress errors about missing files (..a leave me alone I know what am doing option >:( :lol:.). That and the identical file name options should get you your wish (of coming back later to add JS/CSS). What do you think?

 

15 minutes ago, bernhard said:

please don't be mad about me picking on so little things.

On the contrary! I value your honest and helpful feedback! ^-^:).

 

16 minutes ago, bernhard said:

that's just the proof that i'm using your module a lot those days ;)

Exactly :).

  • Like 1
Link to comment
Share on other sites

looks like somebody starts liking the file option :D;)

On 24.7.2017 at 10:18 PM, kongondo said:

Maybe we can add an option to suppress errors about missing files (..a leave me alone I know what am doing option >:( :lol:.). That and the identical file name options should get you your wish (of coming back later to add JS/CSS). What do you think?

yes, that's what i want :) i try to explain what i was talking about in the last 2 postings:

imagine you are working on a project with some runtime markup fields... it starts with easy markup, some html. you create your field, set the option to render a field in a specified folder and you're fine. lets say we store it in RM/fields/myfield.php; so far so good.

imagine you continue working on your project... your project grows and your field needs some more styling. we need some easy CSS rules for that field. so what to do?

option now:

  • leave your IDE
  • open just another browser tab
  • go to the backend
  • search the field
  • go to the settings
  • put in the path of the CSS
  • create your css file (RM/fields/myfield.css)
  • put in your rules

my way how i did it with my render method for several fields:

  • create your css file (we have a myfield.php, so create a myfield.css in the same folder)
  • put in your rules

that's A LOT easier and fool-proof imho.

the problem with your "we have that option of including files with the same name already" is that it throws an error when the file is not present. imho that harms more than it helps, because the problem is that you can NOT choose this option while setting up the field at the moment, because it would always show the error as long as you don't have (don't need) a css/js file.

i would really really vote for one global option:

Quote

load PHP + CSS + JS files with the same name as the field that are inside the folder /RM/fields/ automatically

this setting could hide all other inputfields, you would not have to change any of your options and have a solution for everybody.

hope that makes my point more clear now :)

Link to comment
Share on other sites

Update: Runtime Markup Version 0.0.4.

Changelog

  1. Enhancements to render/add file feature
  2. Added option to suppress errors if JavaScript and CSS files not found (respectively)
  3. Add /site/modules/this-modules-folder/ as a third option in Files Root Path

Currently available on dev branch only.

@bernhard. Using the combinations of JS/CSS has identical name to this field + their respective 'Suppress Missing JS/CSS Files Errors' should cover the need you've described above (i.e., set up your field once and load PHP + CSS + JS files with the same name as the field that are inside the folder /RM/*). That's as automatic as this is going to get ;).

  • Like 2
Link to comment
Share on other sites

Hi kongondo,

I'm sorry that I have to say that, but I still don't like the solution. It took me some time to understand all the settings, read the instructions carefully, paste in some file paths, ended up with some errors (I pasted the old paths with different root from the autofill for this field)...

I ended up putting this replace hook in my site/ready.php - i guess this will save me, and you, and maybe some others some time...

/**
 * replacement for the original runtimemarkup render method
 */
$wire->addHookBefore('InputfieldRuntimeMarkup::render', function($event) {
  $event->replace = true;
  $field = $event->object;
  
  //so that $page and $pages are locally scoped to the eval
  $process = $this->wire('process'); 
  if($process && $process->className() == 'ProcessPageEdit') $page = $process->getPage();

  $pages = $this->wire('pages');

  // render files that are related to this field
  $root = rtrim($this->wire->config->paths->root,'/');
  $path = '/site/modules/FieldtypeRuntimeMarkup/fields/';
  $file = $root.$path.$field->name;
  if(is_file($file.'.php')) {
    // we found a file in the modules /fields folder, so render it
    $str = wireRenderFile($file, [
      'page' => $page,
      'pages' => $pages,
    ]);
  }
  else {
    // no early reaturn because we load assets later
    if(!$this->runtimeFields) $str = '';
    else $str = eval($this->runtimeFields);
  }

  // load assets related to this field
  if(is_file($file.'.js')) $this->wire->config->scripts->add($path . $field->name . '.js');
  if(is_file($file.'.css')) $this->wire->config->styles->add($path . $field->name . '.css');

  //since we are dealing with custom PHP code but also want to make sure that only markup is returned
  //if eval() returns anything other than a string or an integer, we throw an error (e.g. if an object or array is returned)
  $event->return = "Place your files here: $path<a>{$field->name}.php|css|js</a>";
  if (is_string($str) || is_int($str)) $event->return = $str;
  else $this->error($this->_('Only strings and integers should be returned by your custom code! Check if your code is valid.'));
});

 

With that method the setup is as simple as it can get. no clicking around, no pasting in wrong filenames, no error messages if there is no file...

  • create a new field
  • place it in your template
  • place your files to /fields/myfield.php|css|js

----

another question that cost me quite some time already :(

do you have any idea why this simple code does not work?

if($input->post->submit_save) echo 'saved!';
else echo 'not saved';

using tracy i see that $input->post has no data while $input->get has the url params...

also your example from here does not work any more: 

help would be highly appreciated :)

Link to comment
Share on other sites

2 hours ago, bernhard said:

I'm sorry that I have to say that, but I still don't like the solution.

Maybe our wires are getting crossed somewhere :). I thought the current solution meets both your and other people's/scenarios' needs.

2 hours ago, bernhard said:

/fields/myfield.php|css|js

I still don't understand why users should be forced to save files in one location (/fields/). 

EDIT: In addition, what if I have several RM fields (either in the same or different templates) and wanted those fields to share some base JS and CSS? That's not possible if we force users to name their JS and CSS after their fields.

Maybe I am missing something. Maybe if I saw a graphic/mock-up of how the RM field settings (Details Tab) would look like in your suggested solution, I would get it :). For now, I will let the changes I've made stay as I believe they cater for different scenarios.

2 hours ago, bernhard said:

if($input->post->submit_save) echo 'saved!'; else echo 'not saved';

If you mean within RM, the reason is that $input is not scoped locally. Have a look at this post downward.

If that's not it, please let me know. Thanks.

Edit: Silly me. No, POST should not work. By the time the page is reloaded (a redirect), the POST is gone.  GET, on the other hand, is 'always' ther. For POST, you can JS as a workaround (to listen to 'submit_save').

Edited by kongondo
Clarification
  • Like 1
Link to comment
Share on other sites

no, thats not the reason. i don't know why, but $input seems to work! i was also expecting it NOT to work without $this, but it works for $input->get...

<?php namespace ProcessWire;
$out = '';

bd($input->get);
bd($this->input->get);
bd($this->wire->input->get);
bd($input->post);
bd($this->input->post);
bd($this->wire->input->post);
return;

597b8050aef87_2017-07-2820_18_23-EditPage_Runtastic360v2_dev.thumb.png.03fdd8cbaa34fb23cd7b52691b719ede.png

the one on the top is the $post and the one on the bottom the $get.

I tried it also on a different install. Same behaviour. Really strange... no idea whats going on :(

Link to comment
Share on other sites

Sorry, I'm half asleep :P.

Nope, POST, should not work (a redirect has occurred, the POST is gone). A GET works because it is always there. As a workaround, JS can listen to 'submit_save.' 

Edited by kongondo
  • Like 1
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By LuisM
      Symprowire is a PHP MVC Framework based and built on Symfony using ProcessWire 3.x as DBAL and Service-Provider
      It acts as a Drop-In Replacement Module to handle the Request/Response outside the ProcessWire Admin. Even tough Symfony or any other mature MVC Framework could be intimidating at first, Symprowire tries to abstract Configuration and Symfony Internals away as much as possible to give you a quick start and lift the heavy work for you.
      The main Goal is to give an easy path to follow an MVC Approach during development with ProcessWire and open up the available eco-system.
      You can find the GitHub Repo and more Information here: https://github.com/Luis85/symprowire
      Documentation
      The Symprowire Wiki https://github.com/Luis85/symprowire/wiki How to create a simple Blog with Symprowire https://github.com/Luis85/symprowire/wiki/Symprowire-Blog-Tutorial Last Update
      16.07.2021 // RC 1 v0.6.0 centralized ProcessWire access trough out the Application by wrapping to a Service https://github.com/Luis85/symprowire/releases/tag/v0.6.0-rc-1 Requirements
      PHP ^7.4 Fresh ProcessWire ^3.0.181 with a Blank Profile Composer 2 (v1 should work, not recommended) The usual Symfony Requirements Features
      Twig Dependency Injection Monolog for Symprowire Support for .env YAML Configuration Symfony Console and Console Commands Symfony Webprofiler Full ProcessWire access inside your Controller and Services Webpack Encore support Caveats
      Symfony is no small Framework and will come with a price in terms of Memory Usage and added Overhead. To give you a taste I installed Tracy Debugger alongside to compare ProcessWire profiling with the included Symfony Webprofiler

      So in a fresh install Symprowire would atleast add another 2MB of Memory usage and around 40ms in response time, should be less in production due to the added overhead of the Webprofiler in dev env
       
    • By FireWire
      Hello community!

      I want to share a new module I've been working on that I think could be a big boost for multi-language ProcessWire sites.

      Some background, I was looking for a way for our company website to be efficiently translated as working with human translators was pretty laborious and a lack of updating content created a divergence between languages. I, and several other devs here, have talked about translation integrations and have recognized the power that DeepL has. DeepL is an AI deep learning powered service that delivers translation quality beyond any automated service available. After access to the API was opened up to the US, I built Fluency, a DeepL translation integration for ProcessWire.
      Fluency brings automated translation to every multi-language field in the admin, and also provides a translation tool allowing the user to translate their text to any language without it being inside a template's field. With Fluency you can:
      Translate any plain textarea or text input Translate any CKEditor content (yes, with markup) Translate page names for fully localized URLs on every page Translate your in-template translation function wrapped strings Translate modules Fluency is free, and now so is DeepL
      Since this module was first built DeepL has introduced free Developer accounts that allow anyone to start using Fluency at zero cost and beginning with the version 0.3.0 release Fluency now supports free DeepL accounts. As of June 2021 DeepL supports translation to 26 languages and continues to offer more!
      Installation and usage is completely plug and play. Whether you're building a new multi-language site, need to update a site to multi-language, or simply want to stop manually translating a site and make any language a one-click deal, it could not be easier to do it. Fluency works by having you match the languages configured in ProcessWIre to DeepL's. You can have your site translating to any or all of the languages DeepL translates to in minutes (quite literally).
      Let's break out the screenshots...
      When the default language tab is shown, a message is displayed to let users know that translation is available. Clicking on each tab shows a link that says "Translate from English". Clicking it shows an animated overlay with the word "Translating..." cycling through each language and a light gradient shift. Have a CKEditor field? All good. Fluency will translated it and use DeepL's ability to translate text within HTML tags. CKEditor fields can be translated as easily and accurately as text/textarea fields.

      Repeaters and AJAX created fields also have translation enabled thanks to a JavaScript MutationObserver that searches for multi-language fields and adds translation as they're inserted into the DOM. If there's a multi-language field on the page, it will have translation added.

      Same goes for image description fields. Multi-language SEO friendly images are good to go.

      Creating a new page from one of your templates? Translate your title, and also translate your page name for native language URLs. (Not available for Russian, Chinese, or Japanese languages due to URL limitations). These can be changed in the "Settings" tab for any page as well so whether you're translating new pages or existing pages, you control the URLs everywhere.

      Language configuration pages are no different. Translate the names of your languages and search for both Site Translation Files (including all of your modules)

      Translate all of the static text in your templates as well. Notice that the placeholders are retained. DeepL is pretty good at recognizing and keeping non-translatable strings like that. If it is changed, it's easy to fix manually.

      Fluency adds a "Translate" item to the CMS header. When clicked this opens up a modal with a full translation tool that lets the user translate any language to any language. No need to leave the admin if you need to translate content from a secondary language back to the default ProcessWire language. There is also a button to get the current API usage statistics. DeepL account owners can set billing limitations via character count to control costs. This may help larger sites or sites being retrofitted keep an eye on their usage. Fluency can be used by users having roles given the fluency-translate permission.

      It couldn't be easier to add Fluency to your new or existing website. Simply add your API key and you're shown what languages are currently available for translation from/to as provided by DeepL. This list and all configuration options are taken live from the API so when DeepL releases new languages you can add them to your site without any work. No module updates, just an easy configuration. Just match the language you configured in ProcessWire to the DeepL language you want it to be associated with and you're done. Fluency also allows you to create a list of words/phrases that will not be translated which can prevent items such as brands and company names from being translated when they shouldn't

       
      Limitations:
      No "translate page" - Translating multiple fields can be done by clicking multiple translation links on multiple fields at once but engineering a "one click page translate" is not feasible from a user experience standpoint. The time it takes to translate one field can be a second or two, but cumulatively that may take much longer (CKEditor fields are slower than plain text fields). There may be a workaround in the future but it isn't currently on the roadmap. No "translate site" - Same thing goes for translating an entire website at once. It would be great, but it would be a very intense process and take a very (very) long time. There may be a workaround in the future but it isn't on the roadmap. No current support for Inline CKEditor fields - Handling for CKEditor on-demand hasn't been implemented yet, this is planned for a future release though and can be done. I just forgot about it because I've never really used that feature personally.. Alpha release - This module is in alpha. Releases should be stable and usable, but there may be edge case issues. Test the module thoroughly and please report any bugs via a Github issue on the repository or respond here. Please note that the browser plugin for Grammarly conflicts with Fluency (as it does with many web applications). To address this issue it is recommended that you disable Grammarly when using Fluency, or open the admin to edit pages in a private window where Grammarly may not be loaded. This is an issue that may not have a resolution as creating a workaround may not be possible. If you have insight as to how this may be solved please visit the Github page and file a bugfix ticket.
      Requirements:
      ProcessWire  3.0+ UIKit Admin Theme That's Fluency in a nutshell. A core effort in this module is to create it so that there is nothing DeepL related hard-coded in that would require updating it when DeepL offers new languages. I would like this to be a future-friendly module that doesn't require developer work to keep it up-to-date.
      The Module Is Free
      This is my first real module and I want to give it back to the community as thanks. This is the best CMS I've worked with (thank you Ryan & contributors) and a great community (thank you dear reader).
      DeepL Developer Accounts
      In addition to paid Pro Developer accounts, DeepL now offers no-cost free accounts. Now all ProcessWire developers and users can use Fluency at no cost.
      Learn more about free and paid accounts by visiting the DeepL website. Sign up for a Developer account, get an API key, and start using Fluency today.
      Download & Feedback
      Download the latest version here
      https://github.com/SkyLundy/Fluency-Translation/archive/main.zip
      Github repository:
      https://github.com/SkyLundy/Fluency-Translation
      File issues and feature requests here (your feedback and testing is greatly appreciated):
      https://github.com/SkyLundy/Fluency-Translation/issues
       
      Thank you! ¡Gracias! Ich danke Ihnen! Merci! Obrigado! Grazie! Dank u wel! Dziękuję! Спасибо! ありがとうございます! 谢谢你!

    • By tcnet
      PageViewStatistic for ProcessWire is a module to log page visits of the CMS. The records including some basic information like IP-address, browser, operating system, requested page and originate page. Please note that this module doesn't claim to be the best or most accurate.
      Advantages
      One of the biggest advantage is that this module doesn't require any external service like Google Analytics or similar. You don't have to modify your templates either. There is also no Javascript or image required.
      Disadvantages
      There is only one disadvantage. This module doesn't record visits if the browser loads the page from its browser cache. To prevent the browser from loading the page from its cache, add the following meta tags to the header of your page:
      <meta http-equiv="Cache-Control" content="no-cache, no-store, must-revalidate" /> <meta http-equiv="Pragma" content="no-cache" /> <meta http-equiv="Expires" content="0" /> How to use
      The records can be accessed via the Setup-menu of the CMS backend. The first dropdown control changes the view mode.

      Detailed records
      View mode "Detailed records" shows all visits of the selected day individually with IP-address, browser, operating system, requested page and originate page. Click the update button to see new added records.

      Cached visitor records
      View modes other than "Detailed records" are cached visitor counts which will be collected on a daily basis from the detailed records. This procedure ensures a faster display even with a large number of data records. Another advantage is that the detailed records can be deleted while the cache remains. The cache can be updated manually or automatically in a specified time period. Multiple visits from the same IP address on the same day are counted as a single visitor.

      Upgrade from older versions
      Cached visitor counts is new in version 1.0.8. If you just upgraded from an older version you might expire a delay or even an error 500 if you display cached visitor counts. The reason for this is that the cache has to be created from the records. This can take longer if your database contains many records. Sometimes it might hit the maximally execution time. Don't worry about that and keep reloading the page until the cache is completely created.
      Special Feature
      PageViewStatistic for ProcessWire can record the time a visitor viewed the page. This feature is deactivated by default. To activate open the module configuration page and activate "Record view time". If activated you will find a new column "S." in the records which means the time of view in seconds. With every page request, a Javascript code is inserted directly after the <body> tag. Every time the visitor switches to another tab or closes the tab, this script reports the number of seconds the tab was visible. The initial page request is recorded only as a hyphen (-).

      New in version 1.1.0
      A new feature comes with version 1.1.0 which offers to record user names of loggedin visitors. Just activate "Record user names" and "Record loggedin user" in the module settings.
      Settings
      You can access the module settings by clicking the Configuration button at the bottom of the records page. The settings page is also available in the menu: Modules->Configure->ProcessPageViewStat.
      IP2Location
      This module uses the IP2Location database from: http://www.ip2location.com. This database is required to obtain the country from the IP address. IP2Location updates this database at the begin of every month. The settings of ProcessPageViewStat offers the ability to automatically download the database monthly. Please note, that automatically download will not work if your webspace doesn't allow allow_url_fopen.
      Dragscroll
      This module uses DragScroll. A JavaScript available from: http://github.com/asvd/dragscroll. Dragscroll adds the ability in view mode "Day" to drag the records horizontally with the mouse pointer.
      parseUserAgentStringClass
      This module uses the PHP class parseUserAgentStringClass available from: http://www.toms-world.org/blog/parseuseragentstring/. This class is required to filter out the browser type and operating system from the server request.
    • By clsource
      Inertia Adapter ProcessWire Module
      Hello! Long time no see.
      I created this module so you can use Inertia.js (https://inertiajs.com/) with ProcessWire.
      Description
      Inertia allows you to create fully client-side rendered, single-page apps, without much of the complexity that comes with modern SPAs. It does this by leveraging existing server-side frameworks.
      Inertia isn’t a framework, nor is it a replacement to your existing server-side or client-side frameworks. Rather, it’s designed to work with them. Think of Inertia as glue that connects the two. Inertia comes with three official client-side adapters (React, Vue, and Svelte).
      This is an adapter for ProcessWire. Inertia replaces PHP views altogether by returning JavaScript components from controller actions. Those components can be built with your frontend framework of choice.
      Links
      - https://github.com/joyofpw/inertia
      - https://github.com/joyofpw/inertia-svelte-mix-pw
      - https://inertiajs.com/
      Screenshots


       
    • By sms77io
      Hi all,
      we made a small module for sending SMS via Sms77.io. It supports sending to one and multiple users.
      You can download it from GitHub and follow the instructions on how to install it - it is quite easy. An API key is required for sending, get yours for free @ Sms77 and receive 0,50 €.
      Hope this helps somebody and we are open for improvement suggestions!
       
      Best regards
      André
×
×
  • Create New...