Forum Activity for @michael

michael
@michael
01/15/16 09:45:21PM
7,832 posts

After skin or module updates by the original developer, what happens to customizations?
Design and Skin Customization

researchcooperative:....what happens to customizations after updates to skins and modules.

Another way to ask this question is to ask what kinds of customizations affect just the skin, what kinds affect just a module, and what kinds affect both?

Modules will take care of their own templates, unless you override them. skins can over-ride a modules template.

Docs: "Altering a Modules Template"
https://www.jamroom.net/the-jamroom-network/documentation/development/1051/altering-a-modules-template

So if the skin has NOT altered a modules template, AND the admin user has not altered the modules template, then an update to the module will be there for the skin in its default form to use.

However, since a skin can alter a modules template, and the admin user can alter the modules template via the template editor in the ACP, whatever either of those users chose to change it to, will remain the version in use until they are either reverted to the default or further desired changes are applied.

As for skin, if you clone the skin to a new name, its a new skin so no further changes made to the original skin will effect the cloned skin.

If you use the template editor to make changes to templates in an existing skin, then those overridden templates will stay in use even if there are changes made to the underlying template.

When the skin is updated the updates will be brought into the system, just not used. You can revert to using the original by clicking the RESET button on the particular template you're interested in, see:

Docs: "Using the Template Editor"
https://www.jamroom.net/the-jamroom-network/documentation/development/3183/using-the-template-editor

The other thing that might be desired is to bring the new changes into the overridden template and how you do this depends on where you made the changes in the first place.

If you did it in the file system via the skins files then you're probably a developer and so standard development systems take care of this for you, like using GIT to compare the existing skin with the newly changed skin to see what changed then apply the changes.

If you're doing it via the ACP then you can use the COMPARE button to compare any versions to see what changed and move those changes in line by line as desired.

Because there are many ways to do anything it sometimes becomes hard to answer broad questions as there are many unknowns.
michael
@michael
01/15/16 09:33:33PM
7,832 posts

Need some help with some jamroom variables
Using Jamroom

This code will work in the skins meta.tpl page just above the closure of the head tag:

    <!-- its the signup page -->
{if $_post._uri == '/user/signup'}
    <meta name="twitter:card" content="summary_large_image" />
    <meta name="twitter:site" content="" />
    <meta name="twitter:creator" content="" >
    <meta name="twitter:domain" content="" >
    <meta name="twitter:image" content="" />
    <meta name="twitter:title" content="" />
    <meta name="twitter:description" content="" />
{/if}

    <!-- its the index page -->
{if isset($current_url) && $current_url == $_conf.jrCore_base_url}
    <meta name="twitter:card" content="summary_large_image" />
    <meta name="twitter:site" content="" />
    <meta name="twitter:creator" content="" >
    <meta name="twitter:domain" content="" >
    <meta name="twitter:image" content="" />
    <meta name="twitter:title" content="" />
    <meta name="twitter:description" content="" />
{/if}
michael
@michael
01/15/16 09:21:38PM
7,832 posts

Need some help with some jamroom variables
Using Jamroom

The share buttons are setup to only show on the details page. The details page is setup to show the meta info, so there should be no problem from any of those pages. When you customize the site to show the share buttons from other pages the next step in the customization is to add the share meta stuff if you want that too.

Unless someone has done it and has the code to share and is willing to share it, then the request for help becomes a request to do it, then tell me how its done.
michael
@michael
01/13/16 03:38:36PM
7,832 posts

Need some help with some jamroom variables
Using Jamroom

Eddy:
Thank you @derickhand300, but what would the jamroom variables be for the "image, title and decriptions" tags? I want the meta tags to fill in everything as each page is different.

I want this to promote artist/song/video pages, every artist page has a different image, description. title, just like every song page etc.

Eddy

Your best bet would be to use the ShareThis module's facebook template which is already outputting the variables needed to the headers for the item detail pages.

For pages that are not 'item detail' pages (item detail pages are the page on the profile where the file is shown by itself, the main page for that item), then its harder.

Because a page is built:
* include the header (which is where you want to add information)
* include the body (which is where you infomation is requested)
* include the row template (which is where you infomation is shown)
* include the footer

The information that you're thinking about putting out there for twitter isn't there yet.

@derrickhand300 has a custom module that allows you to write the headers manually for any page which works for these types of pages because the info is added in later.
michael
@michael
01/13/16 03:31:10PM
7,832 posts

Accidentally Deleted A Widget- How Do I Recover It in Site builder?
Using Jamroom

depends on how long its been since it was created. If you made it, then deleted it, then its gone.

If a day or so has gone by, then do an import of the page will get the page back to how it was yesterday.

There is no way to recover one widget from a page though, it would need to be the whole page.

--edit--
actually, there is, because the whole page would be in the datastore, but there is no BUTTON to restore one widget on a particular page.
updated by @michael: 01/13/16 03:32:11PM
michael
@michael
01/12/16 05:58:15PM
7,832 posts

Birthday Notifications
Suggestions

paul:.....
1) As admin, goto your profile settings and click on the Form Designer
2) Create field 'profile_birthday' and select 'date_birthday' as the type, and 'string' for validation. Select group(s) that this is active for. Save......

That part is important.

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

That will allow users to add birthdays to their profile. Right now you dont have birthdays saved in the datastore, (as far as I know) so you need to have the data stored before being able to act on it.
michael
@michael
01/12/16 04:52:13PM
7,832 posts

Testing the Wall Widget
Using Jamroom

The two buttons are:
* the normal embed button that embeds stuff thats on your profile
* a create button that embeds stuff while also adding it to your profile.

Thanks for the info on the tablet, I haven't got one of those.

--edit--
I can see an issue that needs addressing, its how to locate the newer comments and stuff.

Whenever anything is commented on or replies added, that thing comes to the top, but in a busy system it could be hard to locate the new stuff you're interested in. I'll need to think about how to address that. Thanks.
updated by @michael: 01/12/16 04:54:55PM
michael
@michael
01/11/16 07:10:44PM
7,832 posts

Birthday Notifications
Suggestions

Its certainly possible to build with the Form Designer adding the birthday date to their profile form.

Then the {jrCore_list} call calling out people who's birthdays match today.
michael
@michael
01/11/16 07:07:47PM
7,832 posts

question about "Last Login" date
Using Jamroom

After having a look at the code, its firing off of the user_last_login table in the datastore.

That field is updated in a couple of locations, one is in the login submit form.

Another location is when the users session is in 'user start session' where the users details are retrieved because they have asked to be kept logged in.

So the "last login" is when the user last visited the site. If the user visited the site in with a different browser and was not logged in, then that's different though.

Its safe to think that "Last Login" was the last time a member of your site looked at the site in a browser.
  441