[serrato]

Hello, been looking for a way to use *title* of instagram story highlights packages into the filename. The separate highlights folder has the title of the individual story/highlight, but how do I put it into the filename as well? So that, when I move the highlights or story folders into the main profile folder, the filename should retain that it's a "story" file and also it which story or highlight it's from. Which would become a sort of organisation in one folder instead of having multiple folders.

Whenever I use any property like *title* or <jd:orgpackagename> ... nothing works in the filename. It always ends up with "#title#" (literally says "title") or "#jd:orgpackagename#" (literally says it). Is there a place I can see the available tags? That's one part of the problem so unsure whether I'm even trying the right things or not.

Of course, I mean to apply this to all types of stories, not just highlights.

And I suspect this would mean that the normal posts (non-stories or non-highlights) would have to ignore the *title* tag?

[Jiaz]

@serrato: Please see https://support.jdownloader.org/de/k...the-packagizer for all supported dynamic tags. You're looking for

<jd:prop:KEY>

Please provide an example and tell me what "title" you're looking for, then I can check for what property this might be or add support for it

[serrato]

Originally Posted by Jiaz

@serrato: Please see **External links are only visible to Support Staff**... for all supported dynamic tags. You're looking for

Please provide an example and tell me what "title" you're looking for, then I can check for what property this might be or add support for it

To be honest, I am embarrassed to say that I have a tough time trying to understand the packagizer rules page haha. There are some things I understood which I utilised but they are the simple ones.

Anyway, in the instagram plugin, you have

- Post crawler and its package name
- Story crawler and its package name scheme
- Story highlights crawler and its package name scheme
..
- Custom filenames: Filename scheme (don't remember if this is default or I set it, but it is set to *date*_*uploader* - *main_content_id* *orderid*_of_*orderid_max* - *shortcode**ext*)

When any post is crawled (normal, story or story highlights), this custom filename is used.

The package for the normal files is the name of the account (uploader), that's fine.
Stories have their own package and have a prefix so they appear as

"story - uploader"

Story highlights do the same, appearing as

"story highlights - uploader"

This is fine for the separate-package approach, but if the stories and story highlights are moved into the same package as the main, normal posts package, then we lose the identifier for which post is a normal one, or a story, or a story highlight.

So I thought I'd change the custom filename to have a prefix - if it's a story, there would be

"story - "

in it. For example, the aforementioned custom filename

*date*_*uploader* - *main_content_id* *orderid*_of_*orderid_max* - *shortcode**ext*

I tried to make it

*date*_*uploader* - *title* - *main_content_id* *orderid*_of_*orderid_max* - *shortcode**ext*

I did this, because the story and story highlights PACKAGES' naming schemes already have *title* in it:

"story - *uploader*"
"story highlights - *uploader* - *title*"

But if I put *title* into the custom filename scheme for all files, this *title* doesn't do anything. I tried various tags that packagizer lists, but none of them seem to work. Note that I am doing this in the Instagram Plugin's page, not in packagizer.

But if I remove *title* from the row that says "Story Highlights crawler: Custom package name scheme for instagram.com/stories/highlights//", then it removes the title from the package name, so it clearly is working there, but it's not working in the global "Custom filenames: Filename scheme" that is a couple rows below it (and yeah I made sure to select "Custom" for "Filename type for all crawled media items").

Long story short, if the post crawled is a story, I want to add the title of that story to the post (just like its package has it) and same for story highlights.

That way, if I merge all the posts into one package, the individual posts will still contain a label like "story" or "story highlight" and thus you don't need separate packages for stories or story highlights if one doesn't want many packages.

Perhaps you can tell me which tags would work, or if I should make a packagizer rule for this? For these dynamic things I've always struggled so let me know how to go about it

[pspzockerscene]

Using the "title" in file names was not possible.

I've just added support via property "story_title" and tag "*title*".

Wartest du auf einen angekündigten Bugfix oder ein neues Feature?
Updates werden nicht immer sofort bereitgestellt!
Bitte lies unser Update FAQ! | Please read our Update FAQ!
---
Are you waiting for recently announced changes to get released?
Updates to not necessarily get released immediately!
Bitte lies unser Update FAQ! | Please read our Update FAQ!

-psp-

[serrato]

Originally Posted by pspzockerscene

Using the "title" in file names was not possible.

I've just added support via property "story_highlight_title" and tag "*title*".

..

-psp-

Thanks! I assume this will work for non-highlight story as well?

[pspzockerscene]

No.

Correct me if I'm wrong but a "non-highlight-story" is just the current story of a user and that does not have a title?

[serrato]

Originally Posted by pspzockerscene

No.

Correct me if I'm wrong but a "non-highlight-story" is just the current story of a user and that does not have a title?

Yes you're right, but when JD packages stories separately, it is able to do so with a "story" prefix (in the package title, I think it's just hard-coded in the story crawler but it's still added nonetheless), but the files at the moment just have regular filenames. I suppose I could manually add the prefix or through packagizer?

[pspzockerscene]

You can change the names either via Packagizer or in the instagram.com plugin settings.

If you do not want that "story" prefix, change the setting "story crawler: package name[...]" to "custom" and then in the field below, enter you custom package name scheme.
By default, the custom scheme does not include the string "story - " so changing it to custom may already be enough to make it work in the way you'd like to have it.

[serrato]

I mean to say, I do want the "story - " prefix, but I want it to be in the files as well, not just the package. Because once I combine all packages into one, the file names will retain the prefixes indicating if they are normal post (no prefixes), story- or storyhighlight -

[pspzockerscene]

That is not easily possible now.
Here are your options to make it work:

1. Use an EventScripter script and work with the boolean property "is_part_of_story" to separate story- and non-story file items. Whenever an item is part of any story "is_part_of_story" returns true.
2. I could update the plugin that for items that are part of a story without title, the title "story" could be set.

EventScripter forum thread:
https://board.jdownloader.org/showthread.php?t=70525
EventScripter help article:
https://support.jdownloader.org/know...event-scripter

[serrato]

Yup, #2 is exactly what I was thinking.

[pspzockerscene]

Done.

Wartest du auf einen angekündigten Bugfix oder ein neues Feature?
Updates werden nicht immer sofort bereitgestellt!
Bitte lies unser Update FAQ! | Please read our Update FAQ!
---
Are you waiting for recently announced changes to get released?
Updates to not necessarily get released immediately!
Bitte lies unser Update FAQ! | Please read our Update FAQ!

-psp-

[serrato]

Thanks again! And happy new year to all of you ~

[serrato]

OK so for normal stories, it works perfectly, thanks!

For story highlights, it's halfway there. The *title* tag works to bring in the title in the custom filenames, but it's missing the "story highlights" prefix. i.e. for normal stories, the prefix of story is coming, but for story highlights, how do I bring in the "story highlights" prefix?

[pspzockerscene]

Not possible nor planned.
This is on the edge of what is possible using our current basic rename systems.
You would need something like "if item is story item, user name scheme X else Y".

That prefix is just a static text for the [default] stories/stories-highlights package names.

Either statically add it for all items (will also be applied for non-story items) or work with the EventScripter to get it only for story items.

[serrato]

So is it the case that stories and story highlights are different from ig such that you can't do the same for highlights as you did for stories?

[pspzockerscene]

No anything is possible but the amount of work required to do what you want is just too high.
My last post explains, which logic would be required but does not exist in our current rename system (property based conditions).
If more users want the same, we can think about it.

Also as explained, it is already possible using an EventScripter script.

[mgpai]

Originally Posted by serrato

... how do I bring in the "story highlights" prefix?

Script may not be necessary if those files go into package name with "story-highlights" prefix. Create a packagizer rule to prepend the string to file name based on the package name.

[serrato]

Originally Posted by mgpai

Script may not be necessary if those files go into package name with "story-highlights" prefix. Create a packagizer rule to prepend the string to file name based on the package name.

OK I think I got it, thanks. It's a bit less flexible as I can only add a string before or after <jd:orgfilename> and not inside it, but it's okay I guess.

[mgpai]

Originally Posted by serrato

OK I think I got it, thanks. It's a bit less flexible as I can only add a string before or after <jd:orgfilename> and not inside it, but it's okay I guess.

I don't have an IG account to check it, but you should be able to insert it anywhere in the file name with packagizer rule.

If you post your current filename pattern and the desired position of the tag, I/@psp might be able to help.

[pspzockerscene]

mgpai is right; I didn't think about that!

Yes, you could indeed extract that string from the package name and put it into the file names via Packagizer rule.

[serrato]

Well I simply made

Story Highlights - <jd:orgfilename>

<jd:orgfilename> includes the whole string of "date - uploader - extra info - .extension". How would I insert a string in this when it's a monolithic tag? All the other dynamic variables are similar. I can't see any way unless there is a way to further split these dynamic variables into smaller pieces.

[pspzockerscene]

Here is my super basic attempt:

Example highlight story of IG user "50cent":

instagram.com/stories/highlights/17857931737875716/

Title of story: Final Lap Tour

Example rule screenshot:


Example file name output:

story highlights - Final Lap Tour_2023-07-14_50cent - CurqFFXuml4 01_of_79 - -.jpg

[mgpai]

Originally Posted by serrato

How would I insert a string in this when it's a monolithic tag? All the other dynamic variables are similar. I can't see any way unless there is a way to further split these dynamic variables into smaller pieces.

Add your (any) static string (e.g. "story highlights -") in the desired position in the filename pattern of the IG plugin.

Create a packagizer rule:

if package name : contains not : "story highlights -"
and
filename contains : *story highlights -*
then set filename : <jd:orgfilename:1><jd:orgfilename:2>

[serrato]

How does the :1 and :2 stuff work?

BTW, I keep forgetting but this has come up again, in packagizer, if I want to append a string at the end of the packagename, it never works. It just replaces the entire packagename with the string. Actually I think I mentioned it before but yea anyway

in the "... then set" section
I set

Package Name to "<jd:orgpackagename> blah"

instead of appending, it adds it renames the whole packagename to "blah". Is this a bug?

[Jiaz]

Originally Posted by serrato

How does the :1 and :2 stuff work?

those are references to the matching group index from your regex
in easy/simple mode, first * = 1, 2nd * = 2 and so on
in regex mode (checkbox on the right), first matching group (...) = 1, 2nd matching group (...) = 2 and so on

[Jiaz]

Originally Posted by serrato

Package Name to "<jd:orgpackagename> blah"
instead of appending, it adds it renames the whole packagename to "blah". Is this a bug?

<jd:orgpackagename> -> placeholder for original package name, which can be empty

you're looking for

<jd:append>

see https://support.jdownloader.org/de/k...the-packagizer

[serrato]

Originally Posted by Jiaz

<jd:orgpackagename> -> placeholder for original package name, which can be empty

you're looking for
see **External links are only visible to Support Staff**...

I couldn't understand it at all unfortunately. The packagizer listing just says it replaces with previous value where placeholder is used, but that just makes me more confused luls. Could you give an example? At the moment whether I use orgpackagename or append, both just disappear and the string I want to append replaces the whole packagename.

[pspzockerscene]

Let's say your package name is:

something here - some other thing here

Now you do:
If...
package name contains:

* - some other thing here

...then set:
Filename...

<jd:orgpackagename:1> _ <jd:orgfilename>

The string value of <jd:orgpackagename:1> is:

something here

[serrato]

Originally Posted by pspzockerscene

Let's say your package name is:

something here - some other thing here

Now you do:
If...
package name contains:

* - some other thing here

...then set:
Filename...

<jd:orgpackagename:1> _ <jd:orgfilename>

The string value of <jd:orgpackagename:1> is:

something here

Okay but what about the case where I only want to change the packagename? i.e. I want to append a string to the packagename like every packagename ends with "dload". If I do "<jd:orgpackagename> dload" it just ends up with "dload" and removes the original packagename (which usually takes its name from either the file or folder in case of a link being in a folder).

[Jiaz]

@serrato: Please test the given example from pspzockerscene

[Jiaz]

@serrato: Please provide example link!
Not every link does have a package name set by plugin, thus you cannot reference to it because it is empty and that's why

<jd:orgpackagename> dload

will result in

dload

because <jd:orgpackagename> is not available/empty.

We can help best if you do provide:
1.) example link
2.) your rule that doesn't work as expected

[serrato]

Originally Posted by Jiaz

@serrato: Please provide example link!
Not every link does have a package name set by plugin, thus you cannot reference to it because it is empty and that's why

will result in

because <jd:orgpackagename> is not available/empty.

We can help best if you do provide:
1.) example link
2.) your rule that doesn't work as expected

Ah, that might be a problem because I was hoping to make a global rule for any link so I never had a source in mind specifically. Just appending an identifier at the end of every package ever downloaded through jdownloader so that in the event I lose something, I can identify later on that so and so file was downloaded via jdownloader and that helps in organising/finding stuff/mental schema lol.

EDIT: I presumed that since JD eventually figures out a name for any package at all, that appending a string would be simple.

[pspzockerscene]

Originally Posted by serrato

I was hoping to make a global rule for any link[...]
Just appending an identifier at the end of every package ever downloaded through jdownloader

So your plan is to apply a static text to any package name?

Originally Posted by serrato

I presumed that since JD eventually figures out a name for any package at all

The problem is packages that have "no name":
See, JDownloader will either put them into a package name "Various" (based on your settings) or name then after the file name inside.
Example for a link that will end up in a package "without name":

ping.online.net/200Mo.dat

Example link for an item that will end up in a package with a name:

instagram.com/p/DEmNp9oRJns/

This "auto name packages without name" happens after the Packagizer rules are processed which means, you cannot interact with these package names in Packagizer rules because they simply do not exist.
You cannot apply something to a non-existent package name.

However, you could counter this by creating two rules:
Rule 1:
Apply a static text to all packages that have names.

Rule 2:
For packages without names, set the file name as package name and apply your static text.

I've created two rules and exported them.
Download:
workupload.com/file/4mL8TUK9G6t

Screenshots of these rules:

Rule 1:

Spoiler:

Rule 2:

Spoiler:

Rule 1 will work for items with pre-set package names (e.g. instagram links) while rule 2 will work for all items that do not have a package name set.

[serrato]

Originally Posted by pspzockerscene

So your plan is to apply a static text to any package name?


The problem is packages that have "no name":
See, JDownloader will either put them into a package name "Various" (based on your settings) or name then after the file name inside.
Example for a link that will end up in a package "without name":

ping.online.net/200Mo.dat

Example link for an item that will end up in a package with a name:

instagram.com/p/DEmNp9oRJns/

...

Ah yes, I should have said that I have disabled the option to group single files into 'various package' (general settings). So I assume this means that packages with no packagename take thier names from the filename, right?

[pspzockerscene]

I've just edited my recent reply as half of the things I described were wrong.

At this moment there is simply no way to check for "package name is not set".
Without this, the only way for you to do what you are trying to do is to do it via an EventScripter script:
EventScripter forum thread:
https://board.jdownloader.org/showthread.php?t=70525
EventScripter help article:
https://support.jdownloader.org/know...event-scripter

Sorry for the confusion.

[serrato]

Yeah I was just about to write that only one of the two can be enabled and so only one scenario can be taken care of. Both activated at the same time begin conflicting.

No biggie though, thanks for the help so far!

[pspzockerscene]

If you need help with the required EventScripter script, feel free to ask for help in our EventScripter subforum:
https://board.jdownloader.org/forumdisplay.php?f=52

[Jiaz]

Working on easy solution to support this via Packagizer Rules

[serrato]

It seems like story highlights are not being crawled at all as of a few updates (not sure when it started but it's fairly recent). I thought maybe it was packagizer messing with it, but even after disabling my packagizer rule, it errors out on any story highlight.