supremebeing

your case is similar to one of my client’s project where he wanted to sort orderby a field but display a different data in frontend. what I did to resolve it was to add an additional custom field just to display it for each entry. let’s call the field ‘displayname’.

try:

[loop type=timeline field=acf_year orderby=field_num]
     <div class="milestone_year bc">[field displayname]</div>
[/loop]

Cool! Finally a discussion on multisite cross content. So far only loop & loop-count work with blog=id for me.

I’ve tested with diff conditions with for/each by adding blog=id, and found out if both blog sites has the same CPT, custom tax and exact fields, as long as the child/client site has the term name saved exactly like the main site, it’s able to pull custom tax fields from the main site, while the term’s slug/id make reference to child’s native saved tax.

Another example that I’m using and it’s working for me: *say the main site is blog=1

[for blog=1 each=customtax]
[set cterm][each slug][/set]
[pass vars]
[loop blog=1 type=cptpost taxonomy=customtax term={CTERM} fields=title,desc]
{TITLE}: {DESC}
[/loop]
[/pass]
[/for]

Both for and loop must include blog=id parameter; if either 1 is left out will break the result. I don’t have clear explanation why this happens but that was what I got from my testing results.

If more complicated conditional logic is needed to apply for creating content, the workaround I use is to move the CCS to an external file and then save it as php file in a child theme folder. and then either load the file using get_template_file when using a template file, or use [load] shortcode in text editor.

Note:
pls take note applying CCS across multisites will have deep nested [loop] and [for], probably many nested [if] too.

Tips that helps me :
i also discovered by adding – nested syntax eventhough it’s not required will not interfere the contents. But if nested syntax isn’t apply when it is needed definitely breaks the code. So what I do when I create snippets that has a pass: I always add a level down nested syntax to avoid code breaking if code before the snippet has changes such as adding a pass into the whole loop / for.

Then again if the whole thing gets too complicated, always work it out by using the standard wp codex format.

Have you gone to the special page under Dashboard >> Content, where the title says Content Overview which list out the entire info of all db you can retrieve.

Everyone’s wp is setup differently so it’s a bit hard to take my setup as a reference for your question.

If your post isn’t showing, then you may check in the overview page if your post post-type has include the relationship with the tag you entered in the shortcode. This happened to me when I started out using this plugin, when things didn’t work out as I wanted to, I thought this plugin was broken; but after spending a long time checking my codes, only to realize everything was my silly mistakes, either relationship not link or typo.

** Also remember to check the logic how you lay it out. I treat this plugin as a shortener for coding, but its basic layout still follows the actual codings.

Dear Mr. Ofer Wald,
I wanna express that by far your plugin is the best option ever for dynamic content websites that has 0 value for ‘hackers’ trying to be funny to ‘steal’ info that they think it’s valuable. The report do not really concern me as long as the plugin you designed works for me. I just learnt to code 4 months ago due to desperation on making the things I want it to work my way, there’re plenty of things if a user expect to just install and works for everything, then one might say ‘this plugin doesn’t work for me’. I’ve did a lot of work-around and so far it all works out for me.

I would like suggest to all users of this plugin, instead of complaining this plugin doesn’t work; why not explore it, try all possible work around then if still got stuck, post a question on how you want it to work, methods of work around tried, expect to have a discussion thread instead of waiting for answers.