No URL field on page load in Craft 3.5RC3

[daltonrooney]

When custom URLs are the default, the url field isn't visible when the page first loads. Toggling the link type seems to fix the issue:

I believe I'm using the latest 2.0 beta of the linkfield plugin.

[sebastian-lenz]

Hi @daltonrooney, thank you for getting in touch. I've just upgraded my test install to Craft 3.5.0-RC3 and I cannot reproduce your issue, the link fields seem to behave like expected.

Do you see any other weird behaviors on the site, e.g. are there other fields not working properly, are there any outputs in the JavaScript console, etc? Are there other plugins involved on the edit page? I guess this happens when you create a new entry, or does this behavior also show up on existing entries?

[daltonrooney]

Thanks for the reply @sebastian-lenz. This behavior seems to be universal, across new entries, existing entries, and I just found the same behavior in globals that were previously working in 3.4:

In this case it's link field inside a matrix. The Entry selection is not preserved after the edit page reloads. No obvious messages in the Console or in the web.log file.

[daltonrooney]

I thought it might be useful to include the markup of the field that is being generated when the page is first loaded:

<div id="fields-registerLink-field" class="field width-100" aria-describedby="fields-registerLink-field-instructions" data-type="lenz\linkfield\fields\LinkField">
    <div class="heading">
      <label id="fields-registerLink-label" class="" for="registerLink"><span class="primary-label">Register Link</span><span class="alt-label"><code>registerLink</code></span></label>
      <div id="fields-registerLink-field-instructions" class="instructions">
        <p>Full URL, including https://</p>
      </div>
    </div>
    <div class="input ltr">
      <div class="linkfield withSettings" id="fields-registerLink-registerLink">
        <div class="linkfield--field">
          <div class="linkfield--type">
            <div class="select">
              <select id="fields-registerLink-type" name="fields[registerLink][type]">
                <option value="empty">
                  (No link)
                </option>
                <option value="url" selected>
                  Url
                </option>
              </select>
            </div>
          </div>
          <div class="linkfield--typeOptions">
            <div class="linkfield--typeOption url hidden">
              <input type="url" id="fields-registerLink-cpForm-url-linkedUrl" class="text fullwidth" name="fields[registerLink][cpForm][url][linkedUrl]" value="" autocomplete="off">
            </div>
            <div class="linkfield--typeOption hidden"></div>
          </div>
        </div>
        <div class="linkfield--settings">
          <div id="fields-registerLink-customText-field" class="field">
            <div class="heading">
              <label id="fields-registerLink-customText-field-label" class="" for="fields-registerLink-customText">Custom link text</label>
            </div>
            <div class="input ltr">
              <input type="text" id="fields-registerLink-customText" class="text fullwidth" name="fields[registerLink][customText]" value="" autocomplete="off" placeholder="Custom link text">
            </div>
          </div>
        </div>
      </div>
    </div>
  </div>

So I guess one question is why the hidden attribute has been added to <div class="linkfield--typeOption url hidden">?

[sebastian-lenz]

Thank you for the additional infos. After playing around further in the control panel by recreating the field configuration above I've been able to reproduce the issue. It seems to be a new behavior introduced by Craft 3.5.

I've contacted the Craft team to figure out whether the changed behavior was intended: craftcms/cms#6478

I'll keep you updated.

[daltonrooney]

@sebastian-lenz I saw that Brandon added the related ticket to the 3.6 milestone. Do you think there's an interim solution for this issue? Is there another way I should be setting up my link fields to avoid the problem?

[curtishenson]

Was there a regression with this in the Craft 3.5 release?

Seemed to work fine in the RC's and now I'm seeing this exact behavior. Wasn't this commit supposed to fix it?

[daltonrooney]

Confirmed, still not working for me in 3.5.0.

[mark-chief]

Do you think this will be “fixed” before 3.6? It’s going to stop me from updating to 3.5!

[sebastian-lenz]

Yes, this can be fixed and I'll do it as soon as possible. I was hoping the change in Craft CMS finds its way into the release but it unfortunately did not make it. I am currently on summer vacation so please give me some time to find a time slot to look into this.

[sebastian-lenz]

I've just released version 2.0.0-beta.10 containing the fix.

[curtishenson]

Confirmed working for me. Thanks!

[sebastian-lenz]

Great, thank you for the feedback. I'll close this issue for now. If you encounter any other problems, please feel free to open a new issue.