flydev

Yes

Did you took a look at their doc ? There are plenty of components examples with markup usage & co.

Hi Paul, lets try to get started with a basic flow. Create a file called mytable.php in the root directory (along side the index.php file) and paste the following code : Then In your template file put the following code : Hope it get you started.

Developing a website or whatever without Tracy is for masochists! Sorry I can't resist!

I don't have ProField here, you should test it now and report back

To enable markdown, you have to install the following core module : ... then you have to apply the Textformatter to your field. Go to the Details tab of your field, select the Textformatter(s) you need then save. Did you mean you clicked/installed the Front-end page editor ? If yes, simply uninstall the module PageFrontEdit. You might need to remove some markup depending on the option you choosen. And welcome

There exist two Pro modules which will help you to build this e-commerce website. Padloper (already mentioned) and Variations : https://variations.kongondo.com (check the tutorial and the video) Also there are two good reads on Snipcart, a tutorial and a case-study - a must read even if you plan to not use Snipcart: https://snipcart.com/blog/processwire-ecommerce-tutorial https://snipcart.com/blog/case-study-ateliers-fromagers-processwire Welcome to the forum @Samk80 and good day to you

@fbg13 Yes absolutely, just copypasted the previous post in case he was using the image field (and btw, the if condition do not make sense, thanks). But should be $form->login_submit->value as $form->login_submit return an object.

@The Frayed Ends of Sanity: modify your hook with the following code : $wire->addHookAfter('LoginRegister::buildLoginForm', function($event) { $form = $event->return; $form->description = false; // Remove the description foreach ($form->children as $field) { // loop form fields if($field instanceof InputfieldSubmit) { // if we reach the submit button then $field->value = 'My Submit'; // change the value } } $event->return = $form; }); Just look at the source code, and learn ProcessWire's hooks. With a little more experience you will be able to find those tricks alone We are happy to help here dude

Here is an alternative of editing the .htaccess file. You could use Jumplinks from @Mike Rockett and manage all of your 404 hits easily (as well all others redirects needed). OT: about the wp-login itself, you could create a page and a template for this, reproduce the WP login form and play a bit with the "hackers" by giving them a nice memes on login submission (last example: https://rockett.pw/jumplinks/examples)

I personally have the following module running to handle users to subscribe and unsubscribe to a newsletter. If your module could take into account @justb3a's module, it would be awesome. It already render the subscription form and create the proper user with the right role on submission.

Guys, could be related to this ? (the last updated answer)

A small addition to what @louisstephens suggested. You could also watch thoses videos to see how easily/quickly you can get a HTML theme working on ProcessWire.

Once again, you can do that by hooking processProfileForm(). Lets say you added a field 'images' to the system user template and you added the 'images' field to the module configuration, e.g. : then in ready.php : wire()->addHookAfter('LoginRegister::processProfileForm', function($e) { $form = $e->arguments[0]; // get the form foreach ($form->children as $field) { if($field instanceof InputfieldImage) { foreach ($field->getAttribute('value') as $value) { wire('user')->images->add($value); } wire('user')->save(); } } }); To show the image on the frontend, you can hook renderProfileForm().

Hi and welcome to the forum. The H2 come from the code of the module on line 518 (link). As it look like there is no option to define your own markup (maybe yes, I am taking my first coffee..), you must change it by translating the file. To do so, first install the core's module LanguageSupport, then translate the module's file : Once saved, you should be able to see the change on your page. Did you mean you already added an image field to the system template user ? if yes, then you need to add the permission profil-edit to the user so he can modify his profile. If its not the case, let us know. If you encounter difficulties, just ask on the forum. Enjoy

use $value... not $options, check my edited post.

In your code $html = $pages->get(6090)->renderField('html_body', array('message' => $reasons, 'stripe_id' => $stripeId)); your option value is the second argument, shouldn't be the third ? $html = $pages->get(6090)->renderField('html_body', 'test', array('message' => $reasons, 'stripe_id' => $stripeId)); // given there is a 'test' markup file and you grab values with : $value['message'] ... not $options. <?php echo $value['message']; ?> <?php echo $value['stripe_id'] ?>

Its because you are storing/sending a Google Account password on your own instead of using a "secure" flow like OAuth2 apps. E.g. using less secure apps is not possible with a 2FA account. https://support.google.com/accounts/answer/6010255?hl=en

Hi pwired, this is exactly what Duplicator do, no more or less about deploying the site. It just help to avoid those repetitive tasks.

I'll give you the url tonight

Yes it make sense, and if I remember correctly we already discussed through PM about this feature. Its not implemented but on the todo list now.

Hey Zeka, the module will be free for the community.

Right, the module doesn't sync changes. It deploy only a full copy of the current website. If I remember correctly, @LostKobrakai made a module which "do some part of that". Let me check the forum and edit this post. @Bergy there is the module (not a simple one!) :

I feel sorry again to make you guys waiting again, I got some works to finish asap, but theses tasks made me test Duplicator extensively and I think its ready for the release. It will not work for each hosting providers, but its a start. Finally, it will come with a new feature: AutoDeploy. With this feature, you will configure the FTP account and database informations, and the module will deploy automatically the web-site without having to run the installer manually.

I also use PHPStorm as main editor for developing locally, but didn't use any of its syncing feature. About the process, I have a staging web-server with a local copy of the client's site where they can see the change on a daily basis. Once the site is edited (I take example on a site without SSH access), I backup the website and send it to the 'live' server trough Duplicator which save a lot of time when deploying the web-site multiple time after change has ben made; It take lower than a minute, depending on your bandwidth. So the workflow is the following: Develop locally FTP the 'local' site to the 'staging' web-server with Duplicator. If the client need some changes, repeat step 1/2. The client is happy ?, FTP the site to the live server with Duplicator. The client have a request ? Backup and retrieve the live website locally, and repeat step from 1 to 4. I must say that using Duplicator save A LOT of time! And even if I have SSH access, I use Duplicator. To keep different version of a website, I use a Gitlab self-hosted server to keep track of the packages made with Duplicator. @Bergy check this screencast on how easy is to deploy your modified website with Duplicator.