Jump to content
horst

Croppable Image 3

Recommended Posts

12 hours ago, adrian said:

I wonder if it has anything to do with using a string for the version number? I am switching my modules over to string version numbers as well, so would be good to know if that is the problem?

normally, the version compare function (should) work correct with strings like "0.9.17". But I can temporary change it, if this would help. (?)

 

I have updated the repo and changed the version from string '0.9.17' to number 100. Does that change anything?

Share this post


Link to post
Share on other sites

on a local test I added a fake module in the root of the modules directory hirarchy and changed the dependencies hirarchy to make it the main module that installs the three others:

/site/modules/CroppableImage3/
/site/modules/CroppableImage3/CroppableImage3.module **
/site/modules/CroppableImage3/FieldtypeCroppableImage3/FieldtypeCroppableImage3.module
/site/modules/CroppableImage3/InputfieldCroppableImage3/InputfieldCroppableImage3.module
/site/modules/CroppableImage3/ProcessCroppableImage3/ProcessCroppableImage3.module

**

Spoiler

<?php namespace ProcessWire;

class CroppableImage3 extends WireData implements Module {
    public static function getModuleInfo() {
        return array(
            'title'    => 'Croppable Image 3 (FAKE-Main-Module)',
            'summary'  => '',
            'author'   => 'Horst Nogajski',
            'version'  => '1.0.0',
            'requires' => 'ProcessWire>=3.0.20, PHP>=5.3.8',
            'installs' => 'FieldtypeCroppableImage3, InputfieldCroppableImage3, ProcessCroppableImage3',
            'icon'     => 'crop'
        );
    }
    public function __construct() {}
    public function init() {}
}

 

 

@adrian: This way it get recognized by the upgrade module. It seems, it has nothing to do with the version is a number or a string.

  • Like 2

Share this post


Link to post
Share on other sites
On 13.2.2017 at 1:59 PM, PWaddict said:

@horst Is it possible to force update the variations when the main crop has been edited without deleting the variations?

No, this is not possible, because if the original update could be with different dimensions than the previous version. If so, there is big potential to crash the image manipulation script with crop settings out of bound of the new original image.

Share this post


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

No, this is not possible, because if the original update could be with different dimensions than the previous version. If so, there is big potential to crash the image manipulation script with crop settings out of bound of the new original image.

Ok thanks for the info.

Let us know if you update the module to be visible on the Upgrades.

Share this post


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

Let us know if you update the module to be visible on the Upgrades.

Uhm, thats sort of a Problem!

I think I cannot simply update it this way, as it may break systems. There are also the check for updates right in the config screen of the module itself, what currently works well. Needs more testing before.

It would be helpful to get some minds / thoughts about this from the veterans.

  • manually update needs to copy all new files over the existing ones
  • (optionally ?) flush the modules cash
  • Install the new wrapper module

I can push it to a test-branch for those who are reading this. But this is not of help for those who want / need updates via PW (individual in module config or via updater module) ??

 

Share this post


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

Uhm, thats sort of a Problem!

I think I cannot simply update it this way, as it may break systems. There are also the check for updates right in the config screen of the module itself, what currently works well. Needs more testing before.

It would be helpful to get some minds / thoughts about this from the veterans.

  • manually update needs to copy all new files over the existing ones
  • (optionally ?) flush the modules cash
  • Install the new wrapper module

I can push it to a test-branch for those who are reading this. But this is not of help for those who want / need updates via PW (individual in module config or via updater module) ??

 

Take your time to do it right.
I'm using the 0.9.17 version and when I check for updates from the module config I get: Session: Error reported by web service: Unable to find that module

EDIT: I've just manually upgrade to 1.0.0 and the issue still exists.

Share this post


Link to post
Share on other sites

what issue? that it is not recognized by the upgrader? this is expected, as i haven't changed anythig than the version number from string "0.9.17" to number 100. :)

 

Share this post


Link to post
Share on other sites
10 hours ago, horst said:

what issue? that it is not recognized by the upgrader? this is expected, as i haven't changed anythig than the version number from string "0.9.17" to number 100. :)

 

Shouldn't be say: Session: Current installed version is already up-to-date like on the other modules?

Share this post


Link to post
Share on other sites

@PWaddict: just to clarify: There are two things here:

The modules version is recognized and the module gets correctly updated via the individual update function in the modules config screen!

The module is not recognized by the third party updater module. This is an issue of that updater module!

What I have tried / described above, is to find a way / workaround without needing to contact the author of the third party module "updater" and ask him if he can debug and change the module to recognize modules that are organized like CI3 too. One way I found out to get recognized by the updater, is to use a wrapper module in the root directory of the module. This will work, AFTER everyone has updated to that version. But with the current situation, before everyone has updated to that version, there may be danger to break systems when silently changing the modules hirarchy and dependencies.

  • Like 1

Share this post


Link to post
Share on other sites

I have a recurring prob on PW 3.0.42 and CI 3 v.1.0.0 on PHP 7.0.16

Anytime I try to edit a page which uses an image crop, I get the following error

Quote

Error: Uncaught Error: Class 'ProcessWire\ProcessCroppableImage3' not found in /var/www/vhosts/my-domain.co.uk/httpdocs/site/modules/CroppableImage3-master/InputfieldCroppableImage3/InputfieldCroppableImage3.module:81
Stack trace:
#0 /var/www/vhosts/my-domain.co.uk/httpdocs/site/modules/CroppableImage3-master/InputfieldCroppableImage3/InputfieldCroppableImage3.module(58): ProcessWire\InputfieldCroppableImage3->getCropLinks(Object(ProcessWire\Pageimage))
#1 [internal function]: ProcessWire\InputfieldCroppableImage3->___renderButtons(Object(ProcessWire\Pageimage), 'images_e875838f...', 0)
#2 /var/www/vhosts/my-domain.co.uk/httpdocs/wire/core/Wire.php(374): call_user_func_array(Array, Array)
#3 /var/www/vhosts/my-domain.co.uk/httpdocs/wire/core/WireHooks.php(549): ProcessWire\Wire->_callMethod('___renderButton...', Array)
#4 /var/www/vhosts/my-domain.co.uk/httpdocs/wire/core/Wire.php(399): ProcessWire\WireHooks->runHooks(Object(ProcessWire\InputfieldCroppableImage3), 'renderButtons', Array)
#5 /var/www/vhosts/my-domain.co.uk/httpdocs/wi (line 81 of /var/www/vhosts/my-domain.co.uk/httpdocs/site/modules/CroppableImage3-master/InputfieldCroppableImage3/InputfieldCroppableImage3.module) 

This error message was shown because: you are logged in as a Superuser. Error has been logged. 

I've refreshed the Modules several times (that worked before) but the problem persisted. I thought perhaps ProCache wasn't helping so I disabled that too temporarily.

Anyone have similar issues ?

Share this post


Link to post
Share on other sites

I think I've found the issue. My uploaded CI folder still have the "-master" name.

Seems to be working now.

Files.png.392fa29b0d54edb87ce7507868fa5447.png

Share this post


Link to post
Share on other sites

Hey @Peter Knight - not sure how you normally install modules, but I would suggest in general going for the class name, upload, or url to zip approaches, which avoid this possibility. Manually downloading and unzipping means you have to watch for this.

  • Like 1

Share this post


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

Hey @Peter Knight - not sure how you normally install modules, but I would suggest in general going for the class name, upload, or url to zip approaches, which avoid this possibility. Manually downloading and unzipping means you have to watch for this.

Hi Adrian

Thanks for the tip.

I normally do install via class name but CI 3 at the time had a more recent version which was only available from GitHub as a ZIP.

At least I think that was the case. Thanks anyway for the help.

Share this post


Link to post
Share on other sites
3 minutes ago, Peter Knight said:

which was only available from GitHub as a ZIP.

Click "Clone or Download" on the Github page, then right-click on the "Download Zip" link and paste that into the "Add Module from URL" install option.

  • Like 2

Share this post


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

Click "Clone or Download" on the Github page, then right-click on the "Download Zip" link and paste that into the "Add Module from URL" install option.

Nice - thanks :)

Share this post


Link to post
Share on other sites

Hey, great module!

Any chance of using the predefined crops via the CKEditor Image Tool? There is even a button for cropping, but it's just the default cropping tool.

Share this post


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

Hey, great module!

Any chance of using the predefined crops via the CKEditor Image Tool? There is even a button for cropping, but it's just the default cropping tool.

Some people do this via HannaCodes or other, self created markup-modules added to the ckeditor boxes.

Something like that:

[[image=theimagename.jpg, crop=thecropname]]

The above could be used by a custom markup module, if you have not installed HannaCode. Assumed you have only one image field on that templates/pages, you have to search for that image in the field and replace that marker with the img tag and src pointing to the crop.

if you have more than one imagefield on a page, you need to add a third param:

[[image=theimagename.jpg, crop=thecropname, fieldname=teaserimages]]

 

If you are willing to get your hands dirty with code and build an own markup module, this is a nice way to learn much about PW and PHP.

Otherwise you can install Hannacode and do it there. Hannacode is a flagship! :)
Pretty usefull for a lot more use cases.

  • Like 2

Share this post


Link to post
Share on other sites

Hello @horst,

First of all, thank you for adapting CroppableImage for ProcessWire 3.x. Modules like this one make ProcessWire into an (even more) robust and flexible option for all kinds of new projects.

I downloaded CroppableImage3 and I was wondering if "free" (variable) width/height is a supported feature in this module (and if not, could it be, pretty please?)

For example, suppose I have this in my field's crop settings:

freeheightcrop,900,0

This would allow the user to create a crop of 900px width and a custom height, so maybe the first image ends up being 900x500, the second one is 900x320, etc. It all depends on the dimensions of the area the user has selected during crop generation.

The calculation would be as follows: get the aspect ratio from the area selected by the user (e.g. a 640x360 area would have a 16:9 aspect ratio). Then, we already know the final width (900px). We calculate the final height using the selected area dimensions and the known final value (i.e. 900 * 360 / 640 = 506.25px --> round down --> 506px final height).

Same idea for width: freewidthcrop,0,900 only this time the width is the variable.

I tried to put freeheightcrop,900,0 into the field configuration and ProcessWire accepted it, but the user's crop won't be saved (it generates a crop that is exactly the same as the original image). Also, when cropping, the upper text that indicates the size of the selection will display "NaNxNaN" until the user selects an area.

Share this post


Link to post
Share on other sites

Hello Horst,

when I'm trying to install the new version I get an error:

( ! ) Notice: Undefined index: sharpening in D:\wamp\www\zaub\site\modules\CroppableImage3\FieldtypeCroppableImage3\FieldtypeCroppableImage3ConfAdaptor.php on line 96
Call Stack
#	Time	Memory	Function	Location
1	0.0040	374752	{main}( )	...\index.php:0
2	0.5650	13487256	ProcessWire\Wire->execute( )	...\index.php:55
3	0.5650	13487528	ProcessWire\Wire->__call( )	...\index.php:55
4	0.5650	13487528	ProcessWire\WireHooks->runHooks( )	...\Wire.php:442
5	0.5650	13487904	ProcessWire\Wire->_callMethod( )	...\WireHooks.php:698
6	0.5650	13487904	ProcessWire\ProcessPageView->___execute( )	...\Wire.php:383
7	0.6430	14965016	ProcessWire\Wire->render( )	...\ProcessPageView.module:205
8	0.6430	14965064	ProcessWire\Wire->__call( )	...\ProcessPageView.module:205
9	0.6430	14965064	ProcessWire\WireHooks->runHooks( )	...\Wire.php:442
10	0.6440	14966448	ProcessWire\Wire->renderPage( )	...\WireHooks.php:782
11	0.6440	14966720	ProcessWire\Wire->__call( )	...\WireHooks.php:782
12	0.6440	14966720	ProcessWire\WireHooks->runHooks( )	...\Wire.php:442
13	0.6440	14967096	ProcessWire\Wire->_callMethod( )	...\WireHooks.php:698
14	0.6440	14967096	ProcessWire\PageRender->___renderPage( )	...\Wire.php:383
15	0.6480	14970688	ProcessWire\Wire->render( )	...\PageRender.module:514
16	0.6480	14970736	ProcessWire\Wire->__call( )	...\PageRender.module:514
17	0.6480	14970736	ProcessWire\WireHooks->runHooks( )	...\Wire.php:442
18	0.6480	14971576	ProcessWire\Wire->_callMethod( )	...\WireHooks.php:698
19	0.6480	14971576	ProcessWire\TemplateFile->___render( )	...\Wire.php:380
20	0.6480	14990608	require( 'D:\wamp\www\zaub\site\templates\admin.php' )	...\TemplateFile.php:268
21	0.6490	14991328	require( 'D:\wamp\www\zaub\wire\modules\AdminTheme\AdminThemeDefault\controller.php' )	...\admin.php:13
22	0.6490	15028512	require( 'D:\wamp\www\zaub\wire\core\admin.php' )	...\controller.php:13
23	0.6590	15076312	ProcessWire\Wire->execute( )	...\admin.php:113
24	0.6590	15076360	ProcessWire\Wire->__call( )	...\admin.php:113
25	0.6590	15076360	ProcessWire\WireHooks->runHooks( )	...\Wire.php:442
26	0.6590	15076736	ProcessWire\Wire->_callMethod( )	...\WireHooks.php:698
27	0.6590	15076736	ProcessWire\ProcessController->___execute( )	...\Wire.php:380
28	0.6770	15619400	ProcessWire\Wire->executeEdit( )	...\ProcessController.php:244
29	0.6770	15619448	ProcessWire\Wire->__call( )	...\ProcessController.php:244
30	0.6770	15619448	ProcessWire\WireHooks->runHooks( )	...\Wire.php:442
31	0.6770	15619824	ProcessWire\Wire->_callMethod( )	...\WireHooks.php:698
32	0.6770	15619824	ProcessWire\ProcessModule->___executeEdit( )	...\Wire.php:380
33	0.6810	15622488	ProcessWire\ProcessModule->renderEdit( )	...\ProcessModule.module:1136
34	0.7190	15742248	ProcessWire\Wire->getModuleConfigInputfields( )	...\ProcessModule.module:1213
35	0.7190	15742520	ProcessWire\Wire->__call( )	...\ProcessModule.module:1213
36	0.7190	15742520	ProcessWire\WireHooks->runHooks( )	...\Wire.php:442
37	0.7190	15742912	ProcessWire\Wire->_callMethod( )	...\WireHooks.php:698
38	0.7190	15742912	ProcessWire\Modules->___getModuleConfigInputfields( )	...\Wire.php:383
39	0.7260	15747744	call_user_func:{D:\wamp\www\zaub\wire\core\Modules.php:3582} ( )	...\Modules.php:3582
40	0.7260	15747744	ProcessWire\FieldtypeCroppableImage3::getModuleConfigInputfields( )	...\Modules.php:3582
41	0.7320	15807072	ProcessWire\FieldtypeCroppableImage3ConfAdaptor->getConfig( )	...\FieldtypeCroppableImage3.module:478

 

Can you help me? I've tried to search for it, but found nothing.

ProcessWire 3.0.62 © 2017

 

Many greets!

Share this post


Link to post
Share on other sites

How did you install / update it?

Update a previous version or first install?

manually or via backend or ...?

Share this post


Link to post
Share on other sites
On 20.5.2017 at 5:38 PM, horst said:

How did you install / update it?

Update a previous version or first install?

manually or via backend or ...?

I deleted an older version manually and than tried to install the newer version via backend. 

Share this post


Link to post
Share on other sites

I have a serious and mysterious problem with CroppableImage3 module since I upgrade to PW 3.0.62.  Since my local copy of the site works perfectly well, I uploaded it to the production site, along with the database. But, I get this error when accessing a page using CroppableImage3.

Exception: There is no crop setting for the template 'promenade' called 'miniature' (in /home/guyvervi/public_html/site/modules/CroppableImage3/FieldtypeCroppableImage3/FieldtypeCroppableImage3.module line 209)

The miniature crop setting IS set. I really does not understand what is going on.

Share this post


Link to post
Share on other sites

I resolved my problem by adding a new crop setting in the my field and changing in my template to the new one... It does not explain why the previous crop setting still works on my local machine... Anyways...

Share this post


Link to post
Share on other sites

Hey, this is a follow up from here:

So, now I have tested every possible combination from ClassNames, filenames and the ModuleName. Every thing will break something when used from an allready installed module with an upgrade through PW.

When I define the main classname in the modules directory as FieldtypeCroppableImage3, the update process fetches the repo, but installs it under site/modules/FieldtypeCroppableImage3, whereas the existing repo stay under site/modules/CroppableImage3! This breaks the whole site, front and backend. The updater doesn't rename the origin repo with a leading dot.

Other solutions tested also broked things.

So, can you please tell me which way to go to bring the module into recognition of the update process?

Share this post


Link to post
Share on other sites

@horst, what if you create a new module file/class in the root of the CroppableImage3 directory named 'CroppableImage3', and that class does nothing apart from auto-install the other classes?

Not ideal of course but might be an okay workaround seeing as you are stuck with the existing directory name.

Share this post


Link to post
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 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 multible repeater items 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 Configurable dialogs for copy and paste 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
      2.0.0
      Feature: Copy multiple items at once! The fundament for copying multiple items was created by @Autofahrn - THX! Feature: Optionally you can disable the copy and/or paste dialog Bug fix: A fix suggestion when additional and normal repeater fields are present was contributed by @joshua - THX! 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 (Version 2.0.0)
      > Github: https://github.com/FlipZoomMedia/InputfieldRepeaterMatrixDuplicate
      > PW module directory: https://modules.processwire.com/modules/inputfield-repeater-matrix-duplicate/
      > Old stable version (1.0.4): https://github.com/FlipZoomMedia/InputfieldRepeaterMatrixDuplicate/releases/tag/1.0.4
    • By Robin S
      A new module that hasn't had a lot of testing yet. Please do your own testing before deploying on any production website.
      Custom Paths
      Allows any page to have a custom path/URL.
      Note: Custom Paths is incompatible with the core LanguageSupportPageNames module. I have no experience working with LanguageSupportPageNames or multi-language sites in general so I'm not in a position to work out if a fix is possible. If anyone with multi-language experience can contribute a fix it would be much appreciated!
      Screenshot

      Usage
      The module creates a field named custom_path on install. Add the custom_path field to the template of any page you want to set a custom path for. Whatever path is entered into this field determines the path and URL of the page ($page->path and $page->url). Page numbers and URL segments are supported if these are enabled for the template, and previous custom paths are managed by PagePathHistory if that module is installed.
      The custom_path field appears on the Settings tab in Page Edit by default but there is an option in the module configuration to disable this if you want to position the field among the other template fields.
      If the custom_path field is populated for a page it should be a path that is relative to the site root and that starts with a forward slash. The module prevents the same custom path being set for more than one page.
      The custom_path value takes precedence over any ProcessWire path. You can even override the Home page by setting a custom path of "/" for a page.
      It is highly recommended to set access controls on the custom_path field so that only privileged roles can edit it: superuser-only is recommended.
      It is up to the user to set and maintain suitable custom paths for any pages where the module is in use. Make sure your custom paths are compatible with ProcessWire's $config and .htaccess settings, and if you are basing the custom path on the names of parent pages you will probably want to have a strategy for updating custom paths if parent pages are renamed or moved.
      Example hooks to Pages::saveReady
      You might want to use a Pages::saveReady hook to automatically set the custom path for some pages. Below are a couple of examples.
      1. In this example the start of the custom path is fixed but the end of the path will update dynamically according to the name of the page:
      $pages->addHookAfter('saveReady', function(HookEvent $event) { $page = $event->arguments(0); if($page->template == 'my_template') { $page->custom_path = "/some-custom/path-segments/$page->name/"; } }); 2. The Custom Paths module adds a new Page::realPath method/property that can be used to get the "real" ProcessWire path to a page that might have a custom path set. In this example the custom path for news items is derived from the real ProcessWire path but a parent named "news-items" is removed:
      $pages->addHookAfter('saveReady', function(HookEvent $event) { $page = $event->arguments(0); if($page->template == 'news_item') { $page->custom_path = str_replace('/news-items/', '/', $page->realPath); } }); Caveats
      The custom paths will be used automatically for links created in CKEditor fields, but if you have the "link abstraction" option enabled for CKEditor fields (Details > Markup/HTML (Content Type) > HTML Options) then you will see notices from MarkupQA warning you that it is unable to resolve the links.
      Installation
      Install the Custom Paths module.
      Uninstallation
      The custom_path field is not automatically deleted when the module is uninstalled. You can delete it manually if the field is no longer needed.
       
      https://github.com/Toutouwai/CustomPaths
      https://modules.processwire.com/modules/custom-paths/
    • By teppo
      Hey folks!
      I'm happy to finally introduce a project I've been working on for quite a while now: it's called Wireframe, and it is an output framework for ProcessWire.
      Note that I'm posting this in the module development area, maily because this project is still in rather early stage. I've built a couple of sites with it myself, and parts of the codebase have been powering some pretty big and complex sites for many years now, but this should still be considered a soft launch 🙂
      --
      Long story short, Wireframe is a module that provides the "backbone" for building sites (and apps) with ProcessWire using an MVC (or perhaps MVVM... one of those three or four letter acronyms anyway) inspired methodology. You could say that it's an output strategy, but I prefer the term "output framework", since in my mind the word "strategy" means something less tangible. A way of doing things, rather than a tool that actually does things.
      Wireframe (the module) provides a basic implementation for some familiar MVC concepts, such as Controllers and a View layer – the latter of which consists of layouts, partials, and template-specific views. There's no "model" layer, since in this context ProcessWire is the model. As a module Wireframe is actually quite simple – not even nearly the biggest one I've built – but there's still quite a bit of stuff to "get", so I've put together a demo & documentation site for it at https://wireframe-framework.com/.
      In addition to the core module, I'm also working on a couple of site profiles based on it. My current idea is actually to keep the module very light-weight, and implement most of the "opinionated" stuff in site profiles and/or companion modules. For an example MarkupMenu (which I released a while ago) was developed as one of those "companion modules" when I needed a menu module to use on the site profiles.
      Currently there are two public site profiles based on Wireframe:
      site-wireframe-docs is the demo&docs site mentioned above, just with placeholder content replaced with placeholder content. It's not a particularly complex site, but I believe it's still a pretty nice way to dig into the Wireframe module. site-wireframe-boilerplate is a boilerplate (or starter) site profile based on the docs site. This is still very much a work in progress, but essentially I'm trying to build a flexible yet full-featured starter profile you can just grab and start building upon. There will be a proper build process for resources, it will include most of the basic features one tends to need from site to site, etc. --
      Requirements and getting started:
      Wireframe can be installed just like any ProcessWire module. Just clone or download it to your site/modules/ directory and install. It doesn't, though, do a whole lot of stuff on itself – please check out the documentation site for a step-by-step guide on setting up the directory structure, adding the "bootstrap file", etc. You may find it easier to install one of the site profiles mentioned above, but note that this process involves the use of Composer. In the case of the site profiles you can install ProcessWire as usual and download or clone the site profile directory into your setup, but after that you should run "composer install" to get all the dependencies – including the Wireframe module – in place. Hard requirements for Wireframe are ProcessWire 3.0.112 and PHP 7.1+. The codebase is authored with current PHP versions in mind, and while running it on 7.0 may be possible, anything below that definitely won't work. A feature I added just today to the Wireframe module is that in case ProcessWire has write access to your site/templates/ directory, you can use the module settings screen to create the expected directories automatically. Currently that's all, and the module won't – for an example – create Controllers or layouts for you, so you should check out the site profiles for examples on these. (I'm probably going to include some additional helper features in the near future.)
      --
      This project is loosely based on an earlier project called pw-mvc, i.e. the main concepts (such as Controllers and the View layer) are very similar. That being said, Wireframe is a major upgrade in terms of both functionality and architecture: namespaces and autoloader support are now baked in, the codebase requires PHP 7, Controllers are classes extending \Wireframe\Controller (instead of regular "flat" PHP files), implementation based on a module instead of a collection of drop-in files, etc.
      While Wireframe is indeed still in a relatively early stage (0.3.0 was launched today, in case version numbers matter) for the most part I'm happy with the way it works, and likely won't change it too drastically anytime soon – so feel free to give it a try, and if you do, please let me know how it went. I will continue building upon this project, and I am also constantly working on various side projects, such as the site profiles and a few unannounced helper modules.
      I should probably add that while Wireframe is not hard to use, it is more geared towards those interested in "software development" type methodology. With future updates to the module, the site profiles, and the docs I hope to lower the learning curve, but certain level of "developer focus" will remain. Although of course the optimal outcome would be if I could use this project to lure more folks towards that end of the spectrum... 🙂
      --
      Please let me know what you think – and thanks in advance!
    • 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. There are 4 different view modes.
      View mode "Day" 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. View mode "Month" shows the total of all visitors per day from the first to the last day of the selected month. View mode "Year" shows the total of all visitors per month from the first to the last month of the selected year. View mode "Total" shows the total of all visitors per year for all recorded years. Please note that multiple visits from the same IP address within the selected period are counted as a single visitor.
      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.
      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 (-).
       
    • By MoritzLost
      This module allows you to integrate hCaptcha bot / spam protection into ProcessWire forms. hCaptcha is a great alternative to Google ReCaptcha, especially if you are in the EU and need to comply with privacy regulations.

      The development of this module is sponsored by schwarzdesign.
      The module is built as an Inputfield, allowing you to integrate it into any ProcessWire form you want. It's primarily intended for frontend forms and can be added to Form Builder forms for automatic spam protection. There's a step-by-step guide for adding the hCaptcha widget to Form Builder forms in the README, as well as instructions for API usage.
      Features
      Inputfield that displays an hCaptcha widget in ProcessWire forms. The inputfield verifies the hCaptcha response upon submission, and adds a field error if it is invalid. All hCaptcha configuration options for the widget (theme, display size etc) can be changed through the inputfield configuration, as well as programmatically. hCaptcha script options can be changed through a hook. Error messages can be translated through ProcessWire's site translations. hCaptcha secret keys and site-keys can be set for each individual inputfield or globally in your config.php. Error codes and failures are logged to help you find configuration errors. Please check the README for setup instructions.
      Links
      Github Repository and documentation InputfieldHCaptcha in the module directory Screenshots (configuration)

      Screenshots (hCaptcha widget)

       
       

       
×
×
  • Create New...