Search the Community
Showing results for tags 'auto'.
Found 4 results
-
Hello, the last few weeks there were four new versions of ProcessWire on the master branch (3.0.226 - 3.0.229) and there seems to be the next one around the corner. I like to upgrade all my ProcessWire websites whenever a new master version is released. Currently I am upgrading around 50 websites, which takes a few hours for all of them. I have skipped a few of the master releases, but was wondering if it would be possible to provide an module for auto upgrades? I know that there is a certain risk involved with auto upgrades and it would not work for the .htaccess file, because this file has its own rules. But upgrading the wire folder and the index.php is usually unproblematic, so those could be auto upgraded. WordPress for example has auto upgrades enabled for patch versions (x.x.1 to x.x.2) if there is not Git present. Currently ProcessWire has no minor versions (x.1.x) and only patch versions (x.x.1), but maybe one could configure in the module settings which branch (dev or master) should be auto upgraded. Maybe this could be a setting in the ProcessWire Upgrade module or an extension: https://processwire.com/modules/process-wire-upgrade/ After the upgrade you could get an email, that your ProcessWire has been upgraded (similar to the Workflow in WordPress). There could also be an option for auto upgrading modules. (for example Tracy Debugger ?) What do you think? Is there some major issue speaking against the option for auto upgrades? Regards, Andreas
-
Hello, this module can publish content of a Processwire page on a Facebook page, triggered by saving the Processwire page. To set it up, configure the module with a Facebook app ID, secret and a Page ID. Following is additional configuration on Facebook for developers: Minimum Required Facebook App configuration: on Settings -> Basics, provide the App Domains, provide the Site URL, on Settings -> Advanced, set the API version (has been tested up to v3.3), add Product: Facebook Login, on Facebook Login -> Settings, set Client OAuth Login: Yes, set Web OAuth Login: Yes, set Enforce HTTPS: Yes, add "https://www.example.com/processwire/page/" to field Valid OAuth Redirect URIs. This module is configurable as follows: Templates: posts can take place only for pages with the defined templates. On/Off switch: specify a checkbox field that will not allow the post if checked. Specify a message and/or an image for the post. Usage edit the desired PW page and save; it will post right after the initial Facebook log in and permission granting. After that, an access token is kept. Download PW module directory: http://modules.processwire.com/modules/auto-fb-post/ Github: https://github.com/kastrind/AutoFbPost Note: Facebook SDK for PHP is utilized.
- 52 replies
-
- 15
-
-
i am using CKEditor and want the design to be like the image below is there a way to get rid auf the <p>-tag around ther inserted image and also keep the <p>-tag around the text? <p>text</p> <p><img></p> <p>text</p> to <p></p> <img> <p></p>
-
Hi, I've been creating a site that has multiple languages but crucially does not use Processwire's awesome inbuilt multi-language support (some background here). My site tree looks something like this... Home - Articles (English) -- Article title -- Article title -- Article title - French -- Articles --- Article title --- Article title --- Article title - German -- Articles --- Article title --- Article title --- Article title etc Now the client want the page slugs to be the same on all languages, so for example an article will have a url like domain.com/articles/name-of-article/ domain.com/fr/articles/name-of-article/ domain.com/de/articles/name-of-article/ etc. The problem... To make life easier for the translators they want the translated articles to auto-generate that page slug. Processwire can't really do that when a translator adds it as it doesn't know which article it is a translation of. Once on the edit screen I have a PageFieldType so the translator has to explicitly select the English version that their post is a translation of. This makes it easy for me in the templates to share content that doesn't need translation such as main image etc. So... I either need a way to extract the slug from the English version and use it for translated versions auotmatically (once the PageFieldType connection is made) overiding any slug that the translators have used. or even better.... I thought a module that automatically creates an unpublished page under /articles/ in all 12 languages with the same page slug when a new English article is added under /articles/. Would this be possible with Processwire? I'm not sure where to start (I'm very much dipping my toes in modules but have used Processwire extensively for projects previously). Any help/guidance would be massively appreciated, thanks!
