Tangible

I’m happy to report that we’ve found a way around this issue!
The problem appears to be something wrong with Flywheel’s NGINX implementation rather than an issue with our plugin (it was complaining about some perfectly valid PHP syntax that works everywhere else), but we changed it anyway just so it would work around whatever bug Flywheel has on its end given how popular that system is.
Hopefully they’ll fix that at some point.

Hi there,

Thanks for taking the time to report this problem!
We’ve indeed seen an issue on local by Flywheel, but have not been able to replicate it in any of the other hosting environments we’ve tested.
Could you let us know which hosting provider and plan this was on so that we can investigate?
PHP/WP version would be helpful as well.

Hi @caffeinatedweb! We will be releasing a premium extension for L&L that adds integrations with LearnDash and several other third-party plugins. It’s still in development and we have some syntax changes that are going to need to be made before we can start offering that extension more broadly. Once the extensions have been thoroughly tested and documented, we’ll release the integration plugin more broadly to the L&L community.

I know this question was already answered on the forum but I thought I’d copy the message here as well in case other people are searching through the WordPress support for an answer to this.

Hi @mariettej! There are two ways to accomplish this that we’ve recently added and they’ll be included in the documentation soon. The first is to use the size attribute with the image field which in your case would look something like <Field image size=thumbnail />. You can also use any of the other three default WordPress image sizes.

Since L&L is an extension of HTML and accepts all the standard HTML tags, the second way to achieve this is to just reference the image_url field inside an img tag and then use any of the regular attributes you’re familiar with in HTML to resize it. Something like <img src="{Field image_url}" alt="{Field title}" />

With that second method, notice the curly braces {}, which is how you can use dynamic tags as the attribute value of some other tag. If you want to learn more about that syntax, check out this post.

Hi there,

Thanks for taking the time to reach out about this, we definitely don’t want people to experience that kind of thing when installing the plugin!
We’re using it extensively in production and haven’t run into it on our own sites, but I just installed Local by Flywheel and can confirm there seems to be an issue with that specific environment.
We’ll look into it, but if you’d like to test it locally in the short term, I’d recommend taking a look at Laragon as it beats Flywheel in speed tests!

Take a look at our discussion forum if you have any other questions or feature requests.

Hi! We’re working hard to meet feature parity with CCS, but I don’t think we’ve got that functionality yet (though you can already target the first or last item in a Loop using <If first> or <If last>).

Usually I recommend making design variations like this with CSS instead of L&L. Would your design be achievable using an :nth-child selector to modify styling at an interval?

I’ll verify that this feature is in the roadmap and mark this thread as resolved for now.

Please feel free to visit our discussion forum if you have any other questions or feature requests.

Hi Johnny!

That all sounds doable with L&L! Let us know if you have any trouble ??

I’m resolving this thread since it doesn’t seem like you need support at the moment. Please feel free to visit our discussion forum if you have any other questions or comments.

Hi Felix,
Sorry for the (very) delayed reply.

Loops & Logic isn’t integrated with WPML in any way, and when they work well together it’s mostly coincidence!

I don’t have enough details to offer a solution, but I’m happy to take a look at it for you. Could you email an export of your template to our support address [email protected], along with a few more details about your use-case?

I’ll close this thread for now and add a solution if we find one ??

Please feel free to visit our discussion forum if you have any other questions.

Hi Besim,

This likely won’t be something we look into in the short term because of the inherent permission/security issues that it would create (you wouldn’t want subsite admins/editors to be able to pull in data from other sites on the network).
Our plugin would literally be banned from the repo if we launched the feature as you described it.
We have ideas of how we can handle looping content from one site to the next securely (on multisite or even between individual sites) so it will eventually be possible but I can’t provide an estimate as to when.

If you have any more questions please head over to the forums which are our official support channel ??

Hi! Are you placing the markup you included directly in the page content? L&L only renders in supported code editors: either a “Tangible Template” module/block/widget in your page builder or the editors under the “Tangible” menu item in the admin. If you’re using the latter you can load the content of a saved template with the [template] shortcode.

Here’s a bit more info on how to use the template shortcode

Please head over to the official discussion/support forums here for any further questions!

We don’t currently plan to support niche themes like Beaver’s. We’re more likely to add popular general-purpose themes like Genesis, GeneratePress, etc.
That being said most of the things on your list are possible regardless of specific theme support in the layout location rules already.
Please head over to the official discussion/support forums here for any further questions!

Hi there,

We do have helpers/GUI features planned, but won’t be able to get around to it in the immediate future as there is a lot of core functionality we need to launch first.
We’ve begun putting together a public roadmap you can consult here:
https://loopsandlogic.com/roadmap/

Hi there,

Templates: Allow you to pull in a self-contained bundle of markup/css/scripts/assets into your content or theme or page builder as needed. Can also be included in other templates or loaded into layouts, etc. Can be useful if several of your layouts have shared elements.

Styles: Allows you to load a SASS stylesheet according to conditional logic rules. This could be useful if instead of having your CSS bundled with your templates/layouts, you prefer to style many templates/layouts using a single stylesheet. It can also be a way to separate concerns if you’re building a library of templates/layouts to use between sites. If you keep the markup versatile enough for all your projects, you can just vary a single unified stylesheet on each client project while keeping all the same templates/layouts between them.

Scripts: Allows you to load a Javascript script according to conditional logic rules. Could be useful if several templates/layouts rely on the same JS. You can also use it for things like adding a Google Analytics tracking code or conditionally loading up Google Maps JS exclusively on the page you want to render a map, etc.

Layouts: Essentially an L&L template applied to a theme template. Much like Gutenberg’s FSE, Elementor’s Theme Builder or Beaver Builder’s Themer, but for applying L&L to theme templates at parts (where compatible). With these you can essentially replace your entire theme with L&L using our location rules.

• This reply was modified 3 years, 1 month ago by Tangible. Reason: bolding sections for legibility

Hi there,

We’ve begun offering options to target parts of Astra and Kadence and will continue to make more options available on that front.
Right now those two themes will offer you the most options with the L&L layout system.
Since we internally use Kadence, you’re most likely to get theme-related features and compatibility on Kadence first with others added as time and popularity permit.

Thank you for the issue description – the screenshot was very helpful.

It was indeed a compatibility issue with PODS. This will be fixed in the next version release, hopefully soon.

If you have any further questions or feedback, please feel free to join our discussion forum.