DL7

Hi All, Hi @teppo, So I got started with some basic testing and ran into some hurdles. Using the FrontEndUser module I managed to get a new user created. But somehow I dont see a way to connect this specific user with a specific profile page (company page) . What I therefor drafted is the following: Create two templates: - Company (Profile information, company infomation, e-mail adres, password (hashed) ) - - Jobapplication (all information for application) With this structure and the API i`m able to login the user and get the profile information into a session. With that I`m able to grab the company information and make a front-end edit page. Furthermore, I can connect the jobapplication to his parent and therefor: -echo all application (being sole children) on the company page - easily post the parent ID with the jobapplication once a new one is created. Some questions with this set-up : Would this work or am I using a workaround and would it be better to do this differently? While using for instance the FormBuilder Module, am I able to -within 1 formpost- create the companypage and then the applicationpage? This would be helpful for the register form where company`s that havent posted anything yet, can create a profile + post a job. Thanks After some more reading and testing, I think I got it. Process changes a bit, but I now understand the flow. What I`ll do is make a login/register page. Then when user logs in (after registration) I can grab the user->ID. He can then update his company data via a front-end form. I`ll attach the used-ID as a field for that (company)page. When that page is created, I can then let the user add a application and I`ll append that to the company page as a child. Think that will work. I think I would even be able to do this in one form-flow.

Hi all, thanks for all the comments. It seems like there is no standard answer to my question ;-) Happy to started this discussion. For what I brainstormed with the current level of Processwire knowledge, I think I will be very feasable to get all the items in here. Having a look at the Skyscraper example (were jobpenings are the skyscrapers) I just need to add one additional layer (being the applicants). The challenge would be to build a dashboard with (front-end) access control were only the company posted the opening is able to post/edit/see the jobopenings and the applicants. My guess is that this would be very feasible using the current RBAC model in Processwire as the login is quite standard. In essence there would only be two roles defined: #1 me as being the admin and 2# as companies that want to post a jobopening. 2# would only be front-end access to the dashboard. When I find the time, I'll set-up a basic version of this website to test if this will work. I`ll keep you updated on the progress. Thanks!

Hi Cacrura, Perhaps I did the first image indeed via the natice cropped function. My apologies for the confusing.

Hi Horst, I totally understand the concept and process. What I dont under however is that after installing the module the first image I cropped the cropped image was visable in the backend under "homepage afbeelding" as being the sole image to be used in the front-end. The cropped overwrote the uploaded image. Of course the orginal image was still available (in the folder structure). No problem, but just wanted to let you know that I had two seperate behaviour using the plugin. I'll try this evening to replicate the first behaviour.

Hi Horst. I mean the image itself. What I would expect is that the cropped image would replace the uploaded one so the one under homepage afbeelding in the gif. Thanks!

First of all: Great module! I just ran into one issue though, perhaps I`m doing something wrong here, but when i`m accept the image the cropped image is created and available in the assets, but in the not showing (or replacing) the image in the backend.

Hi all, Just wanted your opion on the following. I`m creating a jobboard, with the below mentioned features. I`m building this on a home build CMS. The website is like 60% complete. But during some browsing I ran into PW. I downloaded it, and I like the possibilities of it. I`m now wondering if I should continue building the website on top of my own CMS or make the switch to PW. The website contains: - Basic website (showing all jobopenings on the homepage, specific jobopening page, Company page, search) {Should all be possible with PW without custom coding} - Company dashboard -> Login, Post openings, edit openings, edit company page, edit company profile, Check invoicing, Manage applicants {Login should be possible and editing should be possible without custom coding, I`m not sure about the management of applicant however. } - Management of applicants (Applicants can apply on the website. The information gets stored and company can see all the details. Company should be able to define the formfield wich they want to capture; manage the applicants (send emails, changes statuses) I coded all this already within my own CMS/Database. I wondering how I could incorporate this within PW. And what the page/field/template strategy should be. Next to that, I`m wondering how flexible I can utilize PW in the sense of adding custom database tables? Cheers, DL