Jump to content
View in the app

A better way to browse. Learn more.

FMForums.com

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

edit textarea

Featured Replies

Hi

I used the FileMaker Site Assistant to create a website. I found that if I add a scrollbar to the text field in fmp7 the assistant creates a textarea field instead of a text field. This is exactly what I want. The problem I am having is when I go to edit the textarea field none of the data shows up. The fields that are formated as checkbox or text work correctly but not the textarea fields.

Here is a code snippet generated by the assistant:

skills()

Hi

I used the FileMaker Site Assistant to create a website. I found that if I add a scrollbar to the text field in fmp7 the assistant creates a textarea field instead of a text field. This is exactly what I want. The problem I am having is when I go to edit the textarea field none of the data shows up. The fields that are formated as checkbox or text work correctly but not the textarea fields.

Here is a code snippet generated by the assistant:

<xsl:for-each select="fmrs:resultset/fmrs:record/fmrs:field[@name='skills']/fmrs:data">

<xsl:if test="position() != 1"><br/></xsl:if>

<textarea cols="50" rows="5">

<xsl:attribute name="name">skills(<xsl:value-of select="position()"/>)</xsl:attribute>

<xsl:value-of select="fmrs:resultset/fmrs:record/fmrs:field[@name='skills']/fmrs:data"/>

.

.

.

Funny, this forum engine interprets your code and shows a textarea! cool.gif I had to quote it and to remove the td tag to see the code.

The problem is the wrong XPath in your last xsl:value-of line, because it is relative to the XPath in the xsl:for-each select.

So you can replace the <xsl:value-of select="fmrs:resultset/fmrs:record/fmrs:field[@name='skills']/fmrs:data"/> line with <xsl:value-of select="."/>

Actually, if you had translated the XPath in your xsl:value-of statement to an absolute path, you would get probably (have the <xsl:template match="/fmrs:fmresultset"> in mind):D

"/fmrs:fmresultset/fmrs:resultset/fmrs:record/fmrs:field[@name='skills']/fmrs:data/fmrs:resultset/fmrs:record/fmrs:field[@name='skills']/fmrs:data"

Even more funny, my answer is shifted to the right.

  • Author

Martin.

Thank you!!

So am I to assume that the Site Assistant has an error or am I to do something differently? All I did was push the button smile.gif

Again thank you.

  • 1 month later...

I am having this same exact problem. When I use <input> fields then it pulls the information fine, but if the fields are <textarea> fields then it does not pull the information.

Sorry did not see the replies. Got it, thanks.

Create an account or sign in to comment

Important Information

By using this site, you agree to our Terms of Use.

Account

Navigation

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.