but as method 2 is not consistent and generates spaces that are completely different and ugly, use method 1
"New Case"
ah it's throwing the whole template (Next image - button clicked)
@thexmanxyz Thanks for the suggestion to @mahagr on the timestamp “issue” - what you suggested is actually how I have it hardcoded. I can understand that in development mode, the timestamp query may be helpful in forcing css refresh in browsers. But in choosing between those 2 evils (not being able to use our (css) development apps - and evil sticky browser caching) - we would choose for being able to use our dev apps and have timestamp removed.
and check if the template / outlines are assigned correctly
if that is the case it is a problem with your plugin / module
@pnutster You are welcome. Yeah I directly used your code because that is also what should be actually applied in my opinion to the master branch. So that we have the ability to remove the timestamp in development as well as in production. I see absolute no reason to ignore the
asset_timestampsetting in development as it currently is. I do understand your decision why you need that thing. So I also recommended that to @mahagr to look into and overthink the decision of that if statement.
@pnutster If you really want this issue to be addressed please feel free and create an issue on github here. Please simply state there what you already wrote here. You can simply copy most of the text you wrote here. Additionally tag me please on GitHub (thexmanxyz) within that issue. I will jump into the discussion as soon as I get the Github tag notification mail. Thanks.
@greenlanegreb Great that this worked for you. There are ways to circumvent issue with different approaches when using multi-lingual sites (inheritance, different outlines ...)
@thexmanxyz thanks for answering, and sorry for the delay in getting back. I'm working multiple jobs so the time I can dedicate to this is limited.
The particle I want to change the behavior of is WordPress Posts (contentarray.html.twig). The plugin I'm trying to integrate to that particle is a personal version of https://premium.wpmudev.org/blog/wp-content/uploads/2013/10/periodical_publishing.php_.zip, which is a plugin that creates a custom "Issue" taxonomy to allow for the filtering of posts into "Issues", so that the site works like a periodical (with each Issue of the periodical containing its own posts).
So, when a visitor to the site selects an issue, they would only see posts from the issue they selected, no matter where they navigate to, until they select a different issue or visit the "news" section of the site. Of course, all of that works perfectly when within the standard content pages (because their content is handled by the main query), but it does not affect the contentarray Particle, because its content is handled by a custom query.
I could make the plugin just filter all queries, but that would break all the functionality of navigation between issues, the menus and all manner of other things, so what I wanted to do was create an option within the contentarray Particle that allows me to select whether I want a particular instance of that Particle to filter its results through the custom Issue Taxonomy. I can create an option in contentarray.yaml, but I have absolutely no idea what to do with that inside contentarray.html.twig. I don't know how to alter the query in Timber, or even if that's the approach I should be using.
The particle I want to change the behavior of is WordPress Posts (contentarray.html.twig). The plugin I'm trying to integrate to that particle is a personal version of https://premium.wpmudev.org/blog/wp-content/uploads/2013/10/periodical_publishing.php_.zip, which is a plugin that creates a custom "Issue" taxonomy to allow for the filtering of posts into "Issues", so that the site works like a periodical (with each Issue of the periodical containing its own posts).
So, when a visitor to the site selects an issue, they would only see posts from the issue they selected, no matter where they navigate to, until they select a different issue or visit the "news" section of the site. Of course, all of that works perfectly when within the standard content pages (because their content is handled by the main query), but it does not affect the contentarray Particle, because its content is handled by a custom query.
I could make the plugin just filter all queries, but that would break all the functionality of navigation between issues, the menus and all manner of other things, so what I wanted to do was create an option within the contentarray Particle that allows me to select whether I want a particular instance of that Particle to filter its results through the custom Issue Taxonomy. I can create an option in contentarray.yaml, but I have absolutely no idea what to do with that inside contentarray.html.twig. I don't know how to alter the query in Timber, or even if that's the approach I should be using.
gantry5 is really great! I have the only issue that the same page is always displayed different in Firefox and Chrome. What can I do to fix this?
Thanks for advice!
Thanks for advice!
Also your screenshots show the Gantry homepage and none of the available open source templates.
e.g. Helium looks the same on all browsers
@Metal-Frog Hey Tom you need different selectors for each section I would recommend reading this w3schools article
or
#my-section-id-1 h2{color: red;}
#my-section-id-2 h2{color: green;}
@yellowwebmonkey This is my development site: http://rbs.it-ferdinand.de/. All pages in the section "Förderverein" have a blue style. And those headings (H2) should have a different picture ...
bind a class name e.g.
.blue-outline on the HTML body or the content section if it should be for articles only in the layout and then do something like that
.blue-outline h2{color: blue;}
within your
custom.scss
so the actual steps to do:
1.) create a new outline based on your current one (inherit)
2.) set the new outline to the menu points it should apply to (everything under Förderverein)
3.) define a class on the HTML body or your content section
4.) create the respective selector in the
1.) create a new outline based on your current one (inherit)
2.) set the new outline to the menu points it should apply to (everything under Förderverein)
3.) define a class on the HTML body or your content section
4.) create the respective selector in the
custom.scss file depending on the class name you choose, take one of my examples form above
[at]ALL: One message on my own behalf. I'm still maintaining a few Particles / Atoms on my Github profile. I offer them for free and participation is always appreciated. You can find a list of all my Gantry projects on gantryprojects.com or jump directly to my projects listing on Github.
@wmgraf You are welcome. I checked that the zoom effect is not present on helium on my side i checked side by side with Chrome and Firefox. Maybe start Firefox in Private Window/Mode and check again. It might be an issue with your firefox. You can also alternatively try to use the portable version or your current version with a new profile (or just deactivate all custom plugins in the first place).