Forum Activity for @michael

Can I disable "Followers" tab on Forum Profile?

Design and Skin Customization

I think what you're after is when someone arrives at the community profile that they are immediately redirected to the forum.

If that's what you're after, setup another quota, maybe call it 'community'
ACP -> MODULES -> PROFILES -> PROFILES -> TOOLS -> PROFILE QUOTAS -> "community" -> CREATE NEW QUOTA

Then move the /community profile into that quota. Do this by visiting it as an admin user then clicking the gear icon. At the bottom of the PROFILE page you will see the quota.

Next install the "Profile Tweaks" module from the marketplace then visit it at:
ACP -> MODULES -> PROFILES -> PROFILE TWEAKS -> QUOTA CONFIG

Change the "Selected Quota" to be "Community" and the "Allow Customization" to be ON and the "Default Profile Index" to be "Forum"

When ever anyone visits that profile they will go directly to the Forum.

Hiding the side bar and the FOLLOW button will probably take some skin customization or some clever CSS tweaks.

Purging Obsolete Media Files

Jamroom Developers

Worst case I can think of: the user sees an error that is meant for the developers and doesn't understand it. A file not being there when the database expects it to be is not going to topple the system or crash it.

Maybe the item still appears in a list of items then when clicked on it goes to a 404 not found page. You can log 404 errors to the activity log via a setting in the ACP if you want to watch for that.

I often download a database of a site that needs working on from production but do not download the /data/ folder. The result is the site still works but the images show the default image placeholders.

Purging Obsolete Media Files

Jamroom Developers

maybe follow this flow:
Upload a bunch of images to a single jrGallery then it will have a DELETE button for each. That would setup a structure where you can follow the flow of functions that work to delete a single file from a datastore item that contains multiple images.

Im guessing thats what you're after rather than deleting the datastore item itself.

--edit--
the path in the image should be /index.php not /image.php, sorry.

updated by @michael: 08/09/21 08:02:47PM

Purging Obsolete Media Files

Jamroom Developers

"that file" is the hard part. All images that come out on "img src" will first be stored in the cache at /data/cache/(module name).

They will have been put there by processing the master image which is stored with the data at /data/media/(one number)/(another number)/jrAudio_2_image.jpg

something like that ^

That's the image that needs deleting but if you just delete it without deleting the associated datastore entries the system will think it still exists.

So for an image like this one:
your-site.com/blog/image/blog_image/2482/xxxlarge/_v=63f541628547989

its a blog image, its datastore key is 'blog_image' and the datastore _item_id is 2482

Functions that may be useful:
jrCore_get_media_directory
jrCore_get_media_file_url
jrCore_delete_media_file
jrCore_delete_item

Skins and Modules

Off Topic

no, you only need to keep the very latest version.

What is happening is that initially you will have this structure
/modules/jrAudio/(all the module files)
then a new version comes out and the url /modules/jrAudio will turn into a 'symlink' to the newest version which will be put on
/modules/jrAudio-version-1.2.3

The main reason its done like this is because its quicker to copy all the files over from the main code repository to your server into the new directory /modules/jrAudio-version-1.2.3 then once they are all there change it to a symlink.

If instead the flow was to copy the files from the jamroom repository over directly to /modules/jrAudio/index.php or other file then if someone was using that at the time they could see errors.

If its just disk-space you're concerned about you can set the marketplace to just keep 1 version of everything at
ACP -> CORE -> MARKETPLACE -> GLOBAL CONFIG -> GENERAL SETTINGS -> MARKETPLACE VERSIONS

set it to 1.

If you're using the GIT version control system and you want to get /modules/jrAudio-version-1.2.3 back onto its main url of /modules/jrAudio/

then you can use the REBASE MODULE tool found at
ACP -> MODULES -> DEVELOPER -> DEVELOPER TOOLS -> GLOBAL CONFIG -> DEVELOPER SETTINGS -> ENABLE RESET TOOLS

Then
ACP -> MODULES -> DEVELOPER -> DEVELOPER TOOLS -> TOOLS -> REBASE MODULES

updated by @michael: 08/03/21 07:14:19PM

Make white blocks transparent.

Design and Skin Customization

Its probably in list.css, you can also use the "Search Selector" field under STYLE -> BASIC RULE EDITOR -> SEARCH SELECTOR to type in "item" and then look for the one that has ".item"

Alternatively in the Custom Editor at
STYLE -> CUSTOM EDITOR -> CUSTOM CSS
enter

Found bug in metatag module

Design and Skin Customization

The facebook debugger is reporting that page's og:image is fine, its complaining you're missing other different tags.

Found bug in metatag module

Design and Skin Customization

We've updated the meta.tpl in the next version of the jamroom skins, the change is:
got changed to this:

M3U parsing?

Off Topic

ah, gotcha. Yeah that will take some experimenting.

One issue you'll have is that the .m3u file and all the files it points to are probably all in the same directory, something like
list.m3u
file1.mp3
file2.mp3
file3.mp3

but those files are not inside jamroom, so I think you'd need to build a way to import them into jamroom and during that import system you could use the values in the .m3u file to build some jamroom playlists.

You might also consider making a module that takes a jamroom existing playlist and exports it to .m3u.

Just ideas.

How to easily figure out which .tpl to edit?

Design and Skin Customization

Here's some generalizations of where things could be:

site.com/avacardo
if there is a module that uses the module url 'avacardo' then the template that shows that page will most likely be
/modules/xxAvacardo/templates/index.tpl
But if there is no module then the template will probably be at
/skins/(YOUR SKIN)/avacardo.tpl

if the URL is on a profile then its probably controlled by a module, so if the url is
site.com/michael/avacardo
then the template will most likely be
/modules/xxAvacardo/templates/item_index.tpl
but that could have an over-ride template in place at the skin level, so if
/skins/(YOUR SKIN)/xxAvacardo_item_index.tpl
that will be over-riding the modules version.

if there is a number in the URL on a profile then you're likely not looking at a list, but at the DETAIL page of a single item, eg
site.com/michael/avacardo/24
then the template will likely be
/modules/xxAvacardo/templates/item_detail.tpl
but could have an over ride at
/skins/(YOUR SKIN)/xxAvacardo_item_detail.tpl

--edit--
ah yeah on that URL the template names is not so much help. What you have here:
https://example.com/forum/activity/10/username/p=2

is the forum module, so jrForum and the page we're looking at has another / after the module name so its most likely a function. the visibile functions are stored in the index.php file of a module, so
/modules/jrForum/index.php
is the file, then the function name is /activity/ so open that file and look for
function view_jrForum_activity() to see whats going on with the page.
updated by @michael: 07/27/21 03:34:26AM