steveooo

Ahoy captain! I need to hook into 2 areas of ProcessWire: - "view" page link on page tree - "view" page link on page edit (Are there more areas with these "view" links for pages or did I get everyone?) How can I hook into that in order to change the "view" link url? Arrr! It would be great if someone would help me with that! – Pirate GlassedEyes

@LostKobrakai: Well, Dotenv is used so I can write my DB credentials to .env which I can exclude from Git. In the site/config.php, I must then change everything to e.g. getenv('DB_PASSWORD')... So should I include my Dotenv in site/config.php or where would be a good place for that?

Hello, PW 3 uses namespaces and Composer. I wanted to include https://github.com/vlucas/phpdotenv for having a nice .env file with all my DB settings. On 2.7 I simply included everything in the top of the index.php: // Custom require __DIR__ . '/vendor/autoload.php'; $dotenv = new Dotenv\Dotenv(__DIR__); $dotenv->load(); Now, composer is there so I used "composer require vlucas/phpdotenv" and wanted to use it. The current index.php includes the autoloader via: $composerAutoloader = $rootPath . '/vendor/autoload.php'; // composer autoloader if(file_exists($composerAutoloader)) require_once($composerAutoloader); So after that, I tried to add: // Custom $dotenv = new Dotenv\Dotenv(__DIR__); $dotenv->load(); but the error is: Fatal error: Class 'ProcessWire\Dotenv\Dotenv' not found in /var/www/index.php on line 36 It's because on top of the index, there is <?php namespace ProcessWire; So Dotenv is interpreted like a child of ProcessWire. How can I change this? If interesting, here is my composer.json: { "name": "processwire/processwire", "type": "library", "description": "ProcessWire CMS/CMF", "keywords": [ "cms","cmf", "content management system" ], "homepage": "https://processwire.com", "authors": [ { "name": "Ryan Cramer", "email": "ryan@processwire.com", "homepage": "https://processwire.com", "role": "Developer" } ], "require": { "php": ">=5.3.8", "ext-gd": "*", "vlucas/phpdotenv": "^2.2" }, "autoload": { "files": [ "wire/core/ProcessWire.php" ] } } Thanks for your answers!

Ooops..

@LostKobrakai: I like your answer very much but I had to mark diogo's answer as "Solved" and not yours. But thanks for this answer! This helped a lot!

You get me wrong. These were 2 different question. The answer in the README of PW 3 tells that until now, the database did not change. Here I am asking if the database will (future) change until release. 2 different questions.

Hello, will the database structure change until stable release of ProcessWire 3 or won't the database be touched? This would be great to know, Ryan!

Hi tpr! I use it and try finding bugs The thing is: I am starting und create a complex default template for some projects and it would be uncool if some major bugs the projects of my clients. The biggest issue would be that I am creating a lot of fields and templates for this default template and if e.g. the database changes, I would have to start over again or must check what changed and how I can fix it...

I am happy about ProDrafts, but I really like ProcessWire 3 and I can't wait for it to get stable

Well. Any other solutions except "Media Manager"?

Hello, today the beta of ProDrafts was announced. But nothing about ProcessWire 3.0.9 . Will there be an ProcessWire 3 update this week?

Hi Martijn! That's a good answer! Because: files merging via Git is easy on files but on databases not great. How do you know that the database won't change until 3.0 release?

Ryan? Where are you?? We need your answer to this very very important question of mine

Hello guys, I really like ProcessWire, but there are a few features I really miss. One of them is a global media manager with the ease of use like the one in WordPress. There is an old module out there that uses images as pages. So each "image" page has an image title field and a files/image field. I use this kind of media manager on some projects and it kind of works but isn't the best option. I created my own system that also allowed folders. Same as above: A image is a page, but I allowed a "folder" page that can have "folder" or "image" children. So I simulated folders in the page tree: I then created a selectImage and selectImages field, that was a PageTable. With this fields I could select the pages I want on a page to show up. The problems that system has: no support for multi-upload and no batch-like features like moving multiple "images" to another "folder". Now to my idea and the reason I write this post: I thought about this problem and I came up with a theory how it could work (without testing it yet): I create a File or Image field with infinite allowed files/images and I activate the tags property (which is currently only for images) and in the tags I would define the structure of this image. So in real life, all files are on the same level, but I simulate a folder structure by writing the location of a file in the media folder inside the tags property. An example: monkey.jpg with following tags: "zoo__animals". This would mean, that monkey.jpg is simulated to be located in /zoo/animals/monkey.jpg. I then need do hook in the way files are displayed and try to do some magic to create a UI that transforms the flat image/file-list into some nested folder structure like you now it from WordPress. Some problems that can come up: - All files would be in one big folder in assets/files/12345/... A huge folder with lots of images might not be that good in scaling... - File fieldtype currently doesn't support tags. Only images. Well, maybe this idea is total bullsh1t, but maybe someone has got a better idea. I need brains (to eat) to brainstorm! Let me know what you guys think about this chaotic concept of mine! Steve

Adrian, I give you – in the spirit of the Oscars – the golden medal for "Best Off-Topic Comment in February 2016" for this comment! Congratulations, you earned it!

Hello, I read that, but still I do not really get the difference. It would be nice if someone would explain it to me with my example. For example this module is a SEO module (I know MarkupSEO!) that adds a own 'seo_stuff' field to every page. 'seo_stuff' consists of multiple fields like 'seo_description' as textarea and 'seo_keywords' as string. Just a test project for better understanding.

Hello guys, I want to write my first module and I read a lot about fieldtypes and inputfields. I really don't get the difference between the two. I hope someone can explain it to me! Maybe it is easier to tell what I want to do and you could tell me what roles fieldtypes and inputfields have with this module I want to create. I want to create a field that consists of multiple fields (text, textarea). It should be a field that wraps some other fields, so I don't have to install 10 different fields every time. How would I achieve this in regards of fieldtypes and inputfields (and data storage)? Thanks!

Hey folks, I must ask this recurring mother of all questions: Is it now safe to use ProcessWire 3 (currently 3.0.8) for production? Ryan wrote that some people use it on production sites, so I would like to know if you feel that ProcessWire 3 is stable now or if it has some (minor or major) bugs. Thanks for your answers!

I can show you via Skype screencast where the but is and we can find the error via Skype, if you like. But I need your skype name for that

Well. It's still not there. Any idea where the bug is?

Well. This would resolve the issue, but it is not an elegant solution. On a large form, you have to export, import and re-translate the input fields.. and on every change, you have to update both instances... I thought: premium addon with lots of great features, why not start with the basics? I also do not understand why this is a hard thing to implement... Almost every other fieldtype is translatable except the options/select field...

Well, that is not so good for something I need to pay. PW by itself (free product) does support multi-language almost everywhere, so why not 100% in a paid product? It seems somehow wrong...

Hello, I am using FormBuilder and I want to create a multi-language form (1 form for N languages, not 1 separate form for each language!). Everything is translatable except the Select fieldtype. I like to also translate the options in a select field. I found a workaround, but I can not use it (UX reasons for client): Create Pages with Options and use Page fields with select instead of true/raw select fieldtype. Well, this is a workaround, but not a solution. How can I translate my options in select fieldtype? Thank you!

Is it ok to simply replace the /wire/modules/AdminTheme/AdminThemeReno folder? I used Ryan's upgrade module for everything until now...

@renobird: This would be great if you look into it!