Marvin Scharle

Hi David, I'd be glad to take care of AIOM. I'm coming from the South of Germany. I work together with @phil at Conclurer, a web development company. If you want to, I can send you my personal mail address so that we can talk about AIOM. Thanks in advance, Marvin

Hello everyone, Thank you for your fast answers. Looks like there's definitely a need for an extended LDAP module. @teppo: Yes, I'll enhance the module's functionality over time. For ideas and feature wishes, you can just open up tickets on GitHub. Furthermore, if you can extend the module's functionality, you can open up a pull request on GitHub at any time. @horst: Thank you for finding the spelling mistake. I'll fix that one in the next update. @Pete: This is heading in the same direction as teppo's thoughts. Maybe in addition to mapping the groups into different ProcessWire roles, mapping some user-defined Active Directory attributes to ProcessWire user variables could be a nice extension. I'd be glad if we could talk about this in a separat GitHub thread so that this does not interrupt this one. The idea with the GUID is nice, although it needs an additional field in the user model and I'm not sure if that is a proper way to solve this issue. @Nico Knoll: Of course I'm German. How could you be unable to see that. ;-) I work together with @phil at Conclurer.

Hi everybody, I'd like to share a new module with you. Its purpose is to let users sign in with their Active Directory accounts using LDAP. It works similar to the module jimyost released in 2012, but adds some new features to it. You can define specific roles that are applied to new LDAP users Passwords are automatically updated by LDAP Local users still work like a charm You can translate it in the language you want to deploy your ProcessWire site New: Connect to a LDAP server via SSL New: Debug Mode New: Your configuration will be validated on save In my opinion, LDAP authentication is a must-have for ProcessWire being successful in the enterprise. What do you think? Is there a feature you miss? You can find the repository here: https://github.com/conclurer/LdapSignIn You can find the module in the ProcessWire module directory. Thanks in advance! Marvin Edit: Updated to Version 0.5.1 Beta including some minor fixes

Hello everybody, we've just released PassiveCron & cron.pw as a beta version. Also check out the PassiveCron demo module, to learn how to integrate cron.pw inside a module. Follow @cronpw on Twitter to get notified about downtimes and updates. Thank you in advance for your feedback! Marvin

Hi everyone! It's been a little bit of time since the update - the last month was very busy, but we are on the track and planning to release the first public beta version of PassiveCron / cron.pw in the next week. Like the previous previews, I want to share with you two additional features of cron.pw. 1) Dashboard Just like minimize.pw, cron.pw comes with a Dashboard, on which you can control every background task and upgrade your plan. It looks a lot like minimize, although it's blue this time ;-) 2) Task Reports cron.pw lets you take a look at the history of every module's tasks and their executions. This allows you to check out - if necessary - if a certain task has been executed correctly. ... and to enhance your development abilities, cron.pw lets you also inspect every task in detail, including transmitted request parameters and response output. Thank you in advance for your feedback!

Thanks Nico, we are planning to release a beta version soon. Hello guys! It's been a few days since the last update - so I'd really like to tell you about two important additional features of PassiveCron and cron.pw. 1. Enable or disable PassiveCron per Module We hope that module developers will adapt PassiveCron's task handling to improve all ProcessWire sites' speed. But at the same time, we want the user to keep control over the tasks that are able to run in the background. So right from the module's settings page, the user can en- or disable background task handling per module. 2. minimize.pw When PassiveCron launches, we will enhance ProcessImageMinimize / minimize.pw to adapt PassiveCron. This will increase the performance of minimizing one site's images even further. At the same time, this will allow minimize.pw to minimize images even with Pro Cache turned on. Best of all: ProcessImageMinimize's background tasks won't reduce your daily tasks limit! We are very excited about PassiveCron. We are looking forward to share a few screenshots with you in the next update! Thanks and stay tuned! Marvin

Hi again, just as promised: I'm going to give you a glance at two additional features of PassiveCron. 1. Pro Cache Bypass Unlike LazyCron, which is executed parallel to page loads, PassiveCron will be able to execute tasks even while Pro Cache is turned on. So you are able to execute tasks while having great load performance thanks to Pro Cache. 2. No registration needed Unlike ProcessImageMinimize / minimize.pw, there is no need to sign up at our web service. As you install PassiveCron, it will automatically register itself anonymously at cron.pw and just work. In the next weeks we will post more information about PassiveCron and cron.pw as we develop them, so stay tuned.

Can you tell me, what version of ProcessImageMinimize you are using? It looks like the database table is either created incorrectly or there is a problem with your MySQL server. It would be very kind if you could check your database for the process_image_minimize table and remove it if present, and download the current version of ProcessImageMinimize and try to install it again. Can you give me feedback on this issue on our bug tracker on GitHub? I've opened a issue for this. Thanks!

Hi apeisa! Thanks for your great feedback. Such good thoughts really help us, creating just the service, developers want and need. I totally agree with you. Minimize.pw was our first step in the ProcessWire ecosystem. We learned a lot from it, especially creating performant web services, that just work. With things like replication and auto-failover, I think we can guarantee a 99% working service. In the coming days, I'll post more information about how the service is going to work. And opposite to ProcessImageMinimize / minimize.pw, PassiveCron / cron.pw will have an extended open beta period before the first final release. We want to help web developers creating the site with everything they imagine, so this is the way to go. On this one, I'm also right there with you. If everything works fine - and I do think so - we have great ideas to follow up for large projects' needs.

Hi everyone! I'd like to introduce PassiveCron - a module, which allows developers to schedule cronjobs - to you. This will be Conclurer's second Pro Module, following ProcessImageMinimize / minimize.pw. PassiveCron is available now as a beta version. What is it going to do? Have you ever been in a situation, in which ProcessWire ran out of PHP's max_execution_time, because you're doing cool tasks like resizing dozens of images using PIM? Or have you noticed site load performance issues when doing a lot of tasks simultaneously? PassiveCron will fix this by giving developers the ability to schedule tasks to future and / or repeating points in time run tasks asynchronously Isn't this exactly the same as LazyCron? No. LazyCron runs your tasks synchronously as your page loads. So running larger tasks will decrease your page's load performance. Instead of this, PassiveCron is able to run those tasks separately from your site loads, thanks to our new web service cron.pw, which will be released together with PassiveCron. How can I use this in my site / module? We will bundle PassiveCron with an easy-to-use API. Let's say you want to call a specific module action tomorrow at 8:00 am: $cron->tomorrow->at('8:00 am')->run('Class', 'Method'); Or do this specific cleanup task, every night at 3:00 am: $cron->every("day")->at("3:00 am")->run("Class", "Method"); Or just run this one large task asynchronously: $cron->run("Class", "Method"); How much will it cost? We are planning to give every ProcessWire site 200 task executions / day for free. For unlimited task executions per site, it'll be around 5€ (pay once, use forever). During the beta period, no payments will be available. Features overview Easy-to-use API for asynchronous task execution Integrable into existing modules for load time improvements No registration at cron.pw needed Pro Cache will be bypassed En- or disable PassiveCron per module Free minimize.pw background tasks Dashboard with reports per task So, what do you think? Is such a module what you need? Can you imagine additional features or do you have wishes for PassiveCron? Please tell us in the comments. Thank you very much!

We have updated ProcessImageMinimize to version 1.0.2 This version includes some fixes regarding the interaction between the module and minimize.pw's API. Please make sure to update all your sites in order to prevent problems. Additionally, if you have found any bug, please open a ticket. Thank you in advance for your help!

Hi bytesource, thank you for your question. As you can find in ProcessImageMinimize's documentation, the module is using a workflow internally to asynchronously pass and fetch the images to and from our servers. With ProCache enabled, your site is basically cached as static files on your server, so no PHP scripts will be executed - which leads to ProcessImageMinimize not being executed. To cut a long story short, we are currently recommending you to turn off ProCache for one site so that ProcessImageMinimize is able to work. We are currently working on a solution for this, so stay tuned.

We have updated ProcessImageMinimize to version 1.0.1 The update includes a fix for a bug which prevented uploading non-image files in some configuration scenarios. Please install this patch on your site if you have similar issues. Additionally, if you have found any bug, please open a ticket. Thank you in advance for your help!

Important note: Please remove the older version of the ProcessImageMinimize module before installing the new version. If you experience database problems after updating the older version, please run the following SQL query on your database: CREATE TABLE process_image_minimize (image_id VARCHAR(255) NOT NULL PRIMARY KEY, reference VARCHAR(24), state INT(2) NOT NULL, processed VARCHAR(255), force_replace INT(1), created_at INT(11) UNSIGNED NOT NULL, updated_at INT(11) UNSIGNED NOT NULL); CREATE UNIQUE INDEX minimize_api_reference ON process_image_minimize (reference) USING BTREE; CREATE INDEX minimize_api_state ON process_image_minimize (state) USING BTREE; This will manually create the necessary database table.

Hi Martijn, thanks for your feedback and your interest in my SoundCloud module. Can you please change line 116-137 in the module file to the following and tell me, whether it works or not? public function format(&$str) { $str = $this->embedSoundcloud($str); } protected function embedSoundcloud($str) { if (strpos($str, '://soundcloud.com/') === false) return; $regex = '/.*?((?:http|https)(?::\\/{2}[\\w]+)(?:[\\/|\\.]?)(?:[^\\s"]*))/is'; //Url preg_match_all($regex, $str, $matches); //echo var_dump($matches); foreach ($matches[1] as $match) { if (strpos($match, '://soundcloud.com/') === false) continue; $match = str_replace("</p>", "", $match); $soundcloudId = str_replace("https", "http", $match); $oembedURL = "http://soundcloud.com/oembed?".$this->getOembedParameters()."format=json&url=".urlencode($match); $embedCode = $this->getEmbedCode($oembedURL, $soundcloudId); if ($embedCode) $str = str_replace($match, $embedCode, $str); } //exit; return $str; }

I've written a textformatter module for transforming SoundCloud URLs into SoundCloud widgets. It is customizable, so the user is able to select color, auto-play and comment visibility options. Being based on the YouTube/Vimeo textformatter by Ryan, it is working in the same way. I hope you like it. TextformatterSoundcloudEmbed.module

It looks like I figured out, how to deal with it. I just commented out the lines in ProcessPageAdd.module that prove the user's right to access a specific template /* if($t->useRoles && !$user->hasPermission('page-create', $t)) continue; if(!$t->useRoles && !$parentEditable) continue; if(!$t->useRoles && !$user->hasPermission('page-create', $this->parent)) continue; */ Yeah, It's dirty, but it works ;-)

Hi ryan I'm working together with Philipp. I tried to hook your code into the init() method of wire/modules/PagePermissions.module. It results into a fatal error: Notice: Trying to get property of non-object in /home/httpd/vhosts/conclurer.com/subdomains/werkgymnasium/wire/modules/PagePermissions.module on line 251 Notice: Trying to get property of non-object in /home/httpd/vhosts/conclurer.com/subdomains/werkgymnasium/wire/modules/PagePermissions.module on line 251 Warning: Invalid argument supplied for foreach() in /home/httpd/vhosts/conclurer.com/subdomains/werkgymnasium/wire/modules/Process/ProcessPageAdd/ProcessPageAdd.module on line 207 Notice: Trying to get property of non-object in /home/httpd/vhosts/conclurer.com/subdomains/werkgymnasium/wire/modules/PagePermissions.module on line 251 Warning: reset() expects parameter 1 to be array, boolean given in /home/httpd/vhosts/conclurer.com/subdomains/werkgymnasium/wire/modules/Process/ProcessPageAdd/ProcessPageAdd.module on line 230 Catchable fatal error: Argument 1 passed to ProcessPageAdd::getTemplateLabel() must be an instance of Template, null given, called in /home/httpd/vhosts/conclurer.com/subdomains/werkgymnasium/wire/modules/Process/ProcessPageAdd/ProcessPageAdd.module on line 231 and defined in /home/httpd/vhosts/conclurer.com/subdomains/werkgymnasium/wire/modules/Process/ProcessPageAdd/ProcessPageAdd.module on line 241 I hope you are able to find out whats wrong here. Thanks in advance for your help.