Forum Activity for @michael

michael
@michael
08/17/15 06:09:00PM
7,839 posts

Add To Cart Button Appearing For All Items On List


Design and Skin Customization

Try removing your code. Seams like your adding code when its not needed if your getting 2 add to cart buttons.
michael
@michael
08/17/15 05:58:22PM
7,839 posts

When we set the "display" setting in form designer, who are we displaying to?


Using Jamroom

Think I answered that in the other thread:
https://www.jamroom.net/the-jamroom-network/forum/new_posts/32338/shifted-profile-from-one-quota-to-another-and-it-disappeared

But I'll put it here too for completeness.

The Form Designer "display groups" the selections you choose are the people or profiles those settings will display for.

eg:
* profile "indexing" is owned by @someuser who is a 'Master Admin'. The "indexing" profile is in the "Quota A" quota.

If the 'display group' has (quota) Quota A selected, then the form field will show.
If the 'display group' has (group) Master Admin selected, then the form field will show.

Quote:....Are we displaying only to people who can add data? If so, why are there no comparable controls for displaying to let people see the data after it has been entered?....

The Form Designer is for the FORM. It has zero, none at all, control over the output of the data to wherever the data is displayed.

Just because you can put data into the datastore, does not automatically mean that that data is output anywhere at all.

The templates are for outputting data to the user in whatever way you desire.

Form Designer = data into the datstore
Templates = data out of the datastore formatted as desired

Quote:...The present so-called "form designer" is actually a "form field designer", and there is no obvious process for building a whole form and displaying the completed form (with entered data) to different user groups.....

Its a "form designer" the form fields are the individual entities on there, a select box, a check box, these are form fields. semantics,... I know. :)

In the templates you can have it however you want, your not restricted to how I think it should work, because you can make it however You want it to work. No limits.

A small bit of code like this is how you would check in the templates:
{if strlen($item.profile_name) > 0 }
{$item.profile_name}
{/if}

That reads "If the length of the profile name is longer than zero, then display it.".

Which I think is what your after. You can then extend that as much as you like, eg:
{if strlen($item.profile_name) > 0 }
<h1>{$item.profile_name}</h1>
{/if}
That reads "If the length of the profile name is longer than zero, then display it as a main heading".

or
{if strlen($item.profile_name) > 0 }
Hello my name is {$item.profile_name}, nice to meet you!
{/if}
That reads "If the length of the profile name is longer than zero, then display 'hello my name is _____(profile name)________ ' nice to meet you!".
updated by @michael: 08/17/15 05:59:33PM
michael
@michael
08/17/15 05:45:45PM
7,839 posts

Shifted profile from one quota to another and it disappeared


Using Jamroom

researchcooperative:...why should the visibility setting have any effect on the URL of a page?...
Its been fixed in the next version of the profile module.

The assumption in the saving mechanism was that every profile would have a profile_name coming in, so it wasn't checked for. The incoming profile_name is used to create the profile_url so that is what your seeing.

What was happening was that since the profile name was empty, the profile url also became empty, empty translated to no url, so it was redirecting to the top page.
michael
@michael
08/17/15 05:42:52PM
7,839 posts

Shifted profile from one quota to another and it disappeared


Using Jamroom

researchcooperative:...
On further thought... it seems you are talking about the visibility of individual fields in the form designer. ...
Correct, for the Form Designer "display groups" the selections you choose are the people or profiles those settings will display for.

eg:
* profile "indexing" is owned by @someuser who is a 'Master Admin'. The "indexing" profile is in the "Quota A" quota.

If the 'display group' has (quota) Quota A selected, then the form field will show.
If the 'display group' has (group) Master Admin selected, then the form field will show.
michael
@michael
08/17/15 05:36:58PM
7,839 posts

Unable to copy xxxxxxx.tpl to template cache directory error


Using Jamroom

Slow hosting sucks.

I use a local machine for my dev stuff, then upload it to production when its finished.

Nothing worse than being in a good productive flow and have your zone broken out of because you have to wait for something beyond your control. Hate that.
michael
@michael
08/17/15 05:30:45PM
7,839 posts

How do i embed iframes?


Using Jamroom

What is the code your using?
michael
@michael
08/14/15 11:00:56PM
7,839 posts

Profile URL problem


Using Jamroom

you can use your email address + password on Jamroom too, either is accepted.
michael
@michael
08/14/15 10:59:09PM
7,839 posts

Custom php scripts ?


Design and Skin Customization

There's some real cool stuff in Jamroom 5 that makes dealing with the database pretty simple.

The biggest new thing is called a "datastore"

"Datastores"
https://www.jamroom.net/the-jamroom-network/documentation/development/1023/datastores

They're pretty cool in that you don't need to decide on a table structure for your data if you use them.

With flat tables you have:
mod_id | mod_time ........ | mod_??????

Then the values all fixed, but with datastores, its more like an associative array in that you can add more and more stuff to it without needing to change the structure of the database.

Its all geared toward inter-communication between modules, that also allows the end user to extend.

eg: the jrAudio module stores information about an audio file. The jrTag module extends the jrAudio module by allowing users to add tags to audio items. jrAudio doesn't need to know whether jrTag exists or not because jrTag extends jrAudio by adding to its datastore.

Also check out the Form Designer which allows the end user to customize the forms for their own needs.

"Using The Form Designer"
https://www.jamroom.net/the-jamroom-network/documentation/getting-started/1275/using-the-form-designer

If you use jamroom's way of creating forms, then they can be extended by the end user too.
  496