Forum Activity for @michael

2 jamroom sites, 1 database

Installation and Configuration

That info should also show up in the $_SERVER variable array in your modules php files, so you can use that as a trigger to do some switching.

Just to be clear, we haven't built what you want build, so don't have any reference, these are just ideas that a programmer can work with to get the system set up. To have definite answers for you we'd need to build it then tell you how it was built. ( not going to do that )

Tinymce upimg Images and validation

Using Jamroom

Got that sorted in jrUpimg 1.1.6

- border gone
- alt image text from file name
- save dropdown settings choices.

Adding "View All" links beside selected Lucid list module titles.

Design and Skin Customization

Its not difficult, but with CSS you get a LOT of control that can be daunting at first.

CSS is Cascading Style Sheets which is what makes your site look the way it looks.

They are found at:
/skins/( YOUR SKIN )/css/

You will find many .css files in that directory you could put a new rule in any of them, but probably skin.css or style.css would be the most logical perhaps just because of the name of the file.

If you added a class called 'widget_header_links' that would be a descriptive name to use, you could use anything eg:'galan_gal' but it would be easy to forget the association to what it controls.

so your links would then become:

Then in your css you define whatever you want that class to look like:
/skins/( YOUR SKIN )/css/site.css

And they would all be pink.
and they would be pink and bold.

and they would be pink and bold and aligned to the right............

The tool I use to mess around with CSS before writing a line of code is called "Firebug"

You can see it in action here:
Using firebug with the STYLE tab

jrImage with original size, width="original" appears in html

Using Jamroom

Fixed in the next version of jrImage 1.4.15

Added a check to make sure the width="" parameter was a number before setting it.

how to 'lock' main menu bar?

Design and Skin Customization

Strumellia brings up a great point, If you make some of the menu items nested so they only show when you hover over the main item, that would give you more space, so the menu would need to be HUGE for it to be pushed down.

The other option is putting a background color behind the menu so even if it is pushed down, its still the same color:
CSS:

how to 'lock' main menu bar?

Design and Skin Customization

This is something that could be quite difficult to get right. Your talking about having a fixed header, but don't want to specify a height. If you decide on a height, then you can make the #wrapper element that same height from the top of the page so it starts where the top header finishes.

We're also not talking about the standard layout, we're talking about how a browser deals with increasing the size from the size decided by the skin designer, so that introduces a different element.

It would take a bit of playing around with Firebug and testing things to come up with a solution that works.

jrImage with original size, width="original" appears in html

Using Jamroom

There are other widths that are also text values, expect that they would have the same result here no?

eg:
large, xlarge, xxlarge, xxxlarge


updated by @michael: 09/26/16 06:14:45AM

how to 'lock' main menu bar?

Design and Skin Customization

Or you might be talking about the fixed height, in which case go to:
site.com/core/skin_admin/style/skin=jrNingja/file=header.css/section=advanced

and change the #header : height from 75px to 'auto'.

how to 'lock' main menu bar?

Design and Skin Customization

Think you're talking about the header section being positioned 'fixed' to the page on the Ningja skin.

The CSS that controls that is found in:
/skins/jrNingja/css/header.css

On line 1, it looks like this:

To make that purpley-blue section scroll the same as the rest of the page change that to:


and change the spacer to have 0 too in the same file:

Probably best to clone your skin first though to save it getting over-written with skin updates.

New and learning

Using Jamroom

These three are the big 3 when contemplating setup:

Docs: "User"
https://www.jamroom.net/the-jamroom-network/documentation/jamroom-admin-handbook/2982/user

Docs: "Profile"
https://www.jamroom.net/the-jamroom-network/documentation/jamroom-admin-handbook/2984/profile

Docs: "Quota"
https://www.jamroom.net/the-jamroom-network/documentation/jamroom-admin-handbook/2985/quota

Then when you want to add features for those guys to use, you need:

Docs: "Module"
https://www.jamroom.net/the-jamroom-network/documentation/jamroom-admin-handbook/122/module

If you're unsure about how to get where you need to get to and are stuck, try outlining your setup in a forum thread and ask for ideas, eg:

--------
The site I want to setup will have members that post paintings they have done in order to get feedback on them and ideas and criticize in order to improve their painting skills.

A setup for this might be replied to with:
* You only need 1 quota because all members are treated equally
* You'll probably need the comments module, perhaps the forums module, probably the gallery module for users to upload paintings, and perhaps the Photo Album module so your members can collect lists of images they like. Maybe you'll want to add the like module or the rating module, but not both.


With a plan making your ACP decisions will probably become easier.