arjen

Thanks for sharing bitlinguist. You are right, there are several ways to accomplish this. In the case you can control the vhost there is indeed no need for a second vhost file since you can use an alias. The point I tried to explain (in simple steps with basic apache knowledge) is that you need two domains to point to to same server directory.

Thanks again. I updated the correct password.

I've been looking into where the querystring originates, but I'm having trouble finding out. Any pointers to which file(s) the querystring is being build?

Thanks for the feedback LostKobrakai. Is this a bug or did I misconfigure something?

Hi, I got a PageTable which isn't working on the user template. As a superuser everything works fine. As an editor the page from the PageTable gets saved but the but the saved page won't show up in the PageTable field. When the superuser adds the page to the PageTable field the editor can see and edit the page. No console JS errors. Triend two admin themes. Tried Chrome and Firefox. The editor role has access to both user template (view, edit, create, add) and the home template (view, edit, create, add) and has the rights page-edit and user-admin. . The PageTable config is: 1 template pointing to a template with a title and a page field I'm saving the pages under /data/ The funny thing is that when I move the PageTable field to a basic-page (or any other) template everything works as expected. When I move it back to the user template the problem is there again. It has to be some rights issue since it is working for the superuser. I've setup an account with the latest dev where a simple install shows the problem: http://bohrium-bwi.lightningpw.com/processwire/ user: editor password: test123 Try saving the PageTable field on a user. I've added the PageTable to the basic-page too, so you can see it's working there. user: superuser password: superuser1 Any pointers or can anyone confirm? Thanks in advance, Arjen

If you want to see page A on page B you can install the Page References Tab module. This adds another tab in your page showing which pages are linked.

If the use case is to put a label before the field in the page tree you can also use css (:before with "content").

They are indeed very loveable!

It's not complicated, but you have to grasp some basic level on how to interact with API's. Just follow a tutorial like this one. If you got it working, try the WireHttp class you are already trying since that will be a lot cleaner.

I'm in the planning of building one, since I need it for a side project. I won't have time until end of June, but it's on the list.

In my experience booking systems can get pretty complicated quickly. Even the smaller ones can potentially have a lot of interaction with the user which you have to account for. I would first map out the user interaction before deciding which way to approach the functionality. ProcessWire is built to handle this stuff, but there are several ways to build it depending on your exact needs. FormBuilder can be one if you just need a form which needs to be sent by email. If there is backend processing like checking if the trip is available in another system or if you want to prevent duplicate entries you would definately need do some custom PHP (even if you use FormBuilder).

I've never seen a Hello World in the Form Builder. Maybe you could grep "Hello world" in the Form Builder files or in your /site/templates/ files to see where it is coming from?

It seems some FormBuilder files are missing. Have you copied the FormBuilder files as well? They are in: /site/modules/FormBuilder/ Also you can easily reinstall FormBuilder and export the forms from the development version to the live version using the Export tool. I would suggest uploading FormBuilder from the zip file in the Form Builder forum. You might want to post in the FormBuilder forum as well since you can expect a quicker support response by the author.

Hi Buckhorn, Thanks for posting. I will send you a PM.

Hi, We've just landed a nice project with member functionality and we are looking to outsource some work. The skills we are looking for are: Good communication skills At least medior ProcessWire knowlegde (you should be able to build a module) Good understanding of AJAX (you should be able to build small forms and post them with AJAX) Good insight in member based/interaction application development Basic front-end development The development work can be done in English, but please note that the actual system in going to be in the Dutch language (since we first start in English this shouldn't be a problem) Work done here: UX Visual design ProcessWire configuration (i.e. templates/fields/structure) CSS styling Work done by you: Build the application on the front-end with minimal styling but in accordance with the layout (unsemantic layout framework). Build the forms and process the data with the great ProcessWire API Build an AJAX based filter system (example in Dutch) Build a simple subscription layer on top of the application (like Quora, basic functionality is visible to all, extended functionality only to members). Each member role will have additional subscription options which will have to be paid (using Mollie > great API) (this can be done later if we don't have time right now) Save all the processed data to simple text based log files ($log API variable) (this can be done later if we don't have time right now) My estimate that there will be around 40-70 hours of work to be done in PHP. Most of this will have to be done before 1 May. If it's possible you can start earlier please let me know. I know that is tight, but we have a decent budget. If you are interested please let me know. If you are interested please sent me some work you have done plus your hour-rate in a PM. After the initial contact we can setup a chat or Skype call and discuss the project further (both estimate and billing stuff). Thanks!

That is indeed an option, but some kind of drag-and-drop solution would be great. The reason I didn't investigate it futher is because currently there is one Page Edit view and how do you manage a drag-and-drop solution? On a page basis or template basis? What if you make a small change and you have to change 24 other templates as well. I myself don't really see how to abstract those things or how to put an extra "layer" on top of the Page Edit screen. Thanks adrian! Do you have any idea how to order those fields (see my comment above)?

Ah, still I missed it adrian I would find it useful if we can adjust which fields can showed in the tabs. These days I'm running more and more into stuff clients don't really need. For me only name, hide, unpublish should be in settings. But it would be great if we can create or own lay-out. But than again, that's me and my clients So I would find it useful if we can drag-and-drop our own Page Edit page.

How could I've missed this? Thanks ProcessWire Weekly #46 and of course adrian for again making a gem. These tools come in very handy.

Depending on your ProcessWire version, you have to enable the access on template (system template: user) level as well.

You can use ListerPro to change the value of fields. We use this a lot (works really great). Wouldn't argue that it would be a nice addition to Batcher too

Thanks felix for posting. Looking forward to your recipe.

Agreed, when you are used to working with frameworks you can largely build your own logic I was therefore more referring to CMS's like WordPress, Joomla, et cetera.

You will absolutely love ProcessWire and this feeling you got? You will get that a lot . Just unlearn the illogical of other systems and take the most simple route. The thing with ProcessWire is: don't make it harder than is has to be. Good luck with your project.

That's the way I handle this stuff. It's quite easy with the API to loop through all the fields ($fields->find(type=Image|File)) and set the noLang to true. Don't forget to save(). I'm on mobile so no code example, but let me know if you want an actual example.

Me neither. But recently I spoke with a few local designers/developers to whom it did matter. Then came along our client so it was a nobrainer because I could learn something along the way. Will text you to set a small meeting up.