Ideas

Standardize Block with Detail Page (Page Picker Control) Merge Field Behavior with Route

0

Login To Vote

Standardize Block with Detail Page (Page Picker Control) Merge Field Behavior with Route

Core

I was working on the Connection Opportunity Search block and the default Lava template for the Detail Page has this code:

```

{% if DetailPage contains '?' %}

                 <a class="btn btn-default" href="{{ DetailPage }}&OpportunityId={{ opportunity.Id }}" role="button">More Info</a>

        {% else %}

                 <a class="btn btn-default" href="{{ DetailPage }}?OpportunityId={{ opportunity.Id }}" role="button">More Info</a>

{% endif %}

```

I guess this block was from the earlier version of Rock. 

I would like to request to standardize how block behaves with Page Picker, when route is selected, then route should be the returned value so it is not confusing when configuring blocks. I posted a bug report thinking that it was a bug, but I was told that some block don't behave that way and some does.

The Why?

It's always been my personal taste with URL to not show the parameter key as much as possible or when unnecessary. It makes it easier to explain and teach non-tech person without the ? or & and = which makes the url look complicated. Since Content Channel View Block or the Calendar Lava Block allow the selected route, why does the Connection Opportunity Search block won't? 

Photo of Jackson UySubmitted by Jackson Uy, Lake Avenue Church  ·   ·  Core
Remove Votes
Login to add a comment...

Submission Success Tips

Cultivate your ideas for maximum impact with these helpful submission tips that will increase the chances of your brilliant concepts becoming reality.

  • Clear Title: Craft a straightforward and descriptive title that instantly conveys the essence of your idea.
  • Concise Description: Provide an idea description that is succinct, ensuring it effectively communicates the concept without unnecessary verbosity.
  • Provide Additional Details: With a concise description complete, now provide any other details that are needed to better understand the requirements.
  • Thorough Ministry Need Review: Provide a comprehensive overview of the ministry need your idea addresses, emphasizing its significance.
  • Cover the WHY: Clearly articulate the rationale behind your idea, explaining why it's essential and how it aligns with the organization's goals and mission. Oftentimes a clear "why" sheds light into other possible options.