Form Designer -- customizing layout
Using Jamroom
I need to be able to customize the layout on a form.
Is this possible?
updated by @blindmime: 03/31/14 03:18:41AM
Forum Activity for @blindmime
Using Jamroom
I need to be able to customize the layout on a form.
Is this possible?
updated by @blindmime: 03/31/14 03:18:41AM
Business Communication Portal with jr5
Discussions
Thanks, Paul. I've been working on this and it looks promising so far.
Probably a stupid question, but how do I set a recurring event?
Go to ACP on login
Using Jamroom
Is there a way to have users in a quota to be put in the Control Panel on login?
updated by @blindmime: 03/31/14 11:50:30AM
Business Communication Portal with jr5
Discussions
To start, I think it's fairly simple.
I need a public facing general contact form. The public facing website will be "brochure" type with no community aspect. All of the company-to-customer interaction will occur in the backend control panel.
There will be Prospects and Customers.
Site manager receives notification of new Prospect Property. He/She accesses a maintenance proposal form with a list of services to render open pricing fields to enter which are totaled. Open fields for extra services are available. Submitted forms notify the Office who can access the information by search or choosing from a customer/property list. We'll need to a way to mark in-process, submitted-to-prospect, won, or lost proposals. The office prepares a formal proposal outside of the system so prospects do not need account access at this point. However, in the future, we may consider setting up acceptance and payment of the final proposal online. Prospects might receive a monthly newsletter or occasional emails with an opt-out option.
Once the customer has accepted the proposal they become a Customer with account access. The Site Manager logs on and accesses weekly maintenance forms for each Customer in the field, checks off boxes as services are rendered and enters them as complete. The Office is notified on completion. This allows the Office to keep abreast of the weekly maintenance activity of all properties. Customers may have more than one property. The forms will differ from Customer to Customer and Property to Property, depending on the services the customer is receiving. Customer 1 may have a different set of services than Customer 2. Forms will also have open notes fields for special cases where the Site Manager notes extra services needed and completed. Site Manager communication is only with the Office. Customers simply see that weekly maintenance has been completed or not. They also receive notes from the Office of extra service needed which are presented for approval. Perhaps Customer can pay for extra services at this point or it might be added to a monthly invoice which is available for viewing online. The Office is notified of Customer approval and notifies Site Manager.
Customer needs:
Weekly maintenance completion (with email notification)
Extra services needed for approval (with email notification)
Extra services completed/outstanding/need approval
Private Messages to/from Office (with email notification)
Office needs:
-submit Property proposal forms to Site Manager
-receives completed forms for off-system processing
-set up Customer/Property
-set up the weekly Maintenance task form for Site Manager completion
-receive notification of maintenance completion
-receive notification of extra services needed
-notify and get approval for extra services with Customer
-Private Messages to/from Customer, Site Manager (with email notification)
Site Manager needs:
-notification of Property proposals for completion and submission to Office
-notification of Customer/Property acceptance
-access Customers/Property weekly maintenance checklists
-complete and submit weekly maintenance checklists
-notify Office of extra services needed
-receive approval for extra services and access status of outstanding extra services
-Private Messages to/from Office
Any thoughts are greatly appreciated.
Business Communication Portal with jr5
Discussions
I'm working with a client who owns a high-end landscaping architecture company. They have maintenance contracts with dozens of properties and he wants his managers, using an iPad, to be able to 1) fill out a form with cost estimates, 2) fill out weekly maintenance checklists.
I guess I'm trying to get my head around the possibility of using jr5's control panel as a customer portal for the company to communicate with its customers and also internally between management with access to submitted forms, etc.
On a basic jr5 site, when logging into the control panel I see Profile, Account, Notifications. Perhaps a module for maintenance tracking? Monthly invoice?
And then from the management side a way to bring up any client and upload an invoice, fill out a maintenance sheet, etc.
Would j45 be a good choice for building something like what I'm thinking? Any thoughts or insights into tackling such a project would be helpful. I haven't had a chance to do more than overview module building, so I'm still getting a handle and manipulating jr5.
updated by @blindmime: 03/18/14 03:47:23PM
skin cloning issue redux
Using Jamroom
Brian, it appears if the cloned skin is named something like "bbElastic" it's OK. But if I precede "Elastic" with three characters like "bfbElastic" then the include file is messed up. Below I named the cloned skin "bfbElastic" but the include.php is calling it jrbElastic:
/**
* jrbElastic_meta
*/
function jrbElastic_skin_meta(){
$_tmp = array(
'name' => 'jrbElastic',
'version' => '1.0.6',
'developer' => 'The Jamroom Network, ©'. strftime('%Y'),
'description' => 'The Default Jamroom 5 Skin - clean and easy to expand',
'support' => 'http://www.jamroom.net/phpBB2'
);
return $_tmp;
}
/**
* jrbElastic_init
* NOTE: unlike with a module, init() is NOT called on each page load, but is
* called when the core needs to rebuild CSS or Javascript for the skin
*/
function jrbElastic_skin_init(){
// Bring in all our CSS files
jrCore_register_module_feature('jrCore','css','jrbElastic','core_html.css');
jrCore_register_module_feature('jrCore','css','jrbElastic','core_grid.css');
I think this corresponds with the cloning issue @iLoveHouseMusic was having in the other thread as well. This has not been fixed in 5.1.22.
skin cloning issue redux
Using Jamroom
As stated in my initial post, I'm running the lastest core version: 5.1.21.
My skins ARE getting cloned. They show up in the dropdown menu and I can select the cloned skin there. It just doesn't show up in the left sidebar list.
It's happening on all 3 of the sites I've tested.
updated by @blindmime: 02/19/14 03:28:33AM
skin cloning issue redux
Using Jamroom
I'm showing the cloned skin directories as 755 and template files as 644. Showing the same in the original skin.
