How can I create a fluxfield to create a link to another page, where the user can chose the page in a pagetree. Something like the Modify Linkfrom the RTE. Is there something?
Or how else would I create a field for a internal link? Just an inputfield where the use can input the PageID is not enough.
One more step would be a field where the user can input an internal link OR an external link.
Have not found any good solution for this problem yet. How do you do it?
You can use a normal text input, but add a link wizard to it. Looks like this:
<flux:field.input
name="link"
label="Link!"
>
<flux:wizard.link/>
</flux:field.input>
To output the link, use one of the ViewHelpers v:(link|uri).typolink from EXT:vhs:
<v:link.typolink configuration="{parameter: link}">
Linktext
</v:link.typolink>
This works for all kinds of links.
Related
I want to get the id of an element in google forms. I found on the internet that it can be done by right clicking on the element and opening inspect element. It is working for older forms but, for new forms, it doesn't show any id attribute. I am posting both images of inspect element.
Old forms:
New forms:
In new form google have replace id with name attribute.So do one thing, write something in textbox then rightclick on textbox and open inspect element, Here you will find item tag with name attribute which is the key you want
For eg,
<input name="entry.123456" >
Maybe I can help you in finding the id's of the element.
After submitting the form you can look for headers{Form Data} in the network section of developer tools.
You will find something like this..
entry.102708304: "Your response"
102708304 is the id..
Hope my answer was useful. Thank You.
Try pressing Ctrl+U when on the Google Website. In Firefox this will show up the complete HTML Code where you can search better. There has to be set an Id, because otherwise the text in the element couldn't be accessed
hi this has changed a bit,
you need to get a pre filled link via 3 dot menu then prefilled link , copy it into an editor and confirm these entries.
I could not find it visible anywhere in the source code and there are a ton of JS names that seem random and 0 name inputs on my form
I would like to create a link to a news-detail-page, but this news-detail-page is on another URL (both pages are in the same typo3-installation).
So for example I list news-article on www.domain1.com, the link to the detailpage shall be www.domain2.com/article/123 (article/123 is just how RealURL build the link).
Right now the link is generated with this code in News/Partials/List/Item.html
{n:link(newsItem: newsItem, settings: settings, uriOnly: 1)}
but this generates a link to: www.domain1.com/article/123.
Best would be if the news viewhelper automaticly determinates where the news-article is coming from (where the news-container is), but it would be also very good if I just could manually say what URL it shall take.
I am using the Advanced Custom Fields Plugin (http://www.advancedcustomfields.com) with the options page add-on so I can use global variables throughout the theme (on multiple pages).
I don't know PHP and I'm trying to get the custom field from the options page by using a shortcode in the content on the different pages inside the WYSIWYG editor.
Is this possible? I can't figure out how to do it after days of trying. Can anyone help? I've tried going to the plugin's support and haven't gotten anything back.
Please Help! I really need to get this working!
References:
http://www.advancedcustomfields.com/docs/functions/using-shortcodes/
http://www.advancedcustomfields.com/add-ons/options-page/
Figured out a way around it. I can just use the shortcode they provide to reference a specific post/page ID which accomplishes the goal of only having to put it in once and it being rendered at multiple pages as long as the shortcode is there and properly formatted.
Use the post_id of option in your shortcode as per this example:
[acf field="myfieldname" post_id="option"]
Block type: Text Block (WYSIWYG field)
Text:
[acf field="NAME-OF-ACF-FIELD" post_id="options"]
Image (Return Format: Image URL) and alt text:
<img src="[acf field='NAME-OF-ACF-FIELD' post_id='options']" alt="[acf field='NAME-OF-ACF-FIELD' post_id='options']" />
I'm trying to place a link on the submit page of my powermail setup.
You'd think this is a simple task, but bear with me.
My Powermail form has 2 hidden fields which are prefilled with a page ID and a page title.
These belong to the page I later want to return to, after having sent the mail. By putting these values in the form, I hoped to have access to them whenever I need them in the process.
I prefill these hidden fields from TypoScript like so:
plugin.tx_powermail {
settings {
setup {
prefill {
// Hidden "back to" page ID. This is the page you may want to return to after sending a mail.
backto = TEXT
backto.data = GP:backTo
backto.if.isTrue.data = GP:backTo
backtotext = TEXT
backtotext.noTrimWrap = |Back to ||
backtotext.data = GP:title
backtotext.if.isTrue.data = GP:title
backtotext.htmlSpecialChars = 1
}
}
}
}
1. Approach
Given that Powermail claims you can now use Fluid ViewHelpers in your content sections, I though, great, let's use the PageViewHelper, like so:
{f:link.page(pageUid:'{backto}')}
But where does my link text go? More inline notation to the rescue!
{backtotext -> f:link.page(pageUid:'{backto}')}
Rendered Result
Seems like the inline notation is not fully supported. I thought I was smart by simply using:
{f:link.page(pageUid:'{backto}')}{backtotext}
But this leaves the <a> tag open, which has very undesirable effects...
So - No link for me!
2. Approach
So I thought I would simply construct the link in TypoScript and render it on the page via
{f:cObject(typoscriptObjectPath:'lib.myBackLink')}
But I can't see any way to access the variables from the (sent) Powermail form in TS. So I don't have access to the page ID or title.
3. Approach
So I thought, if the default PageViewHelper only wants to render its children as its content, maybe I can roll my own ViewHelper that accepts the content as a parameter!
But how would I make that ViewHelper known to the system so that I can use it in my customized Powermail templates?
I've only used Fluid inside of my extensions before. It was obvious how Fluid would look up the correct ViewHelper by name, by what if I want to use a ViewHelper in my fileadmin folder hierarchy?
4. Approach
So, why not just use a normal link by using {backtotext} in the RTE?
TYPO3 realizes, that that is an illegal reference, and quickly turns the link into:
And the resulting output will simply not be a link.
So, that doesn't work either.
OK, so I change the target to {backtotext} (removed a slash). Now the URL is no longer recognized as internal and is marked with data-htmlarea-external="1". This causes my link to actually be fully evaluated and rendered (yay).
But it is now treated like an external link, RealURL no longer affects it and it is subject to external link _target behavior.
Why is this so difficult? What am I not understanding?
In RTE you have to use <link ###pageid###> instead of <a href="...">.
Have a look into the RTE DB field contents (or hit the no RTE checkbox) on how to use the link elements.
As it turned out, none of the previously attempted solution actually worked.
To get things over with, I just replaced the web section in the PowermailAll template, like so:
Section for Web view
<f:section name="web">
</a>
</f:section>
And then I used the following in my Submit Page content:
{f:link.page(pageUid:'{backto}')}{backtotext}{powermail_all}
Problem solved. I guess...
I have defined some external links to store URLs to which other pages can link to. This way a change of URL by a backend user is reflected sitewide.
I wish to extract these URLs to text to put them them into a newsletter as that would be a better practice than redirecting through the site. How could I go about this ?
You may use a placeholder in the rte link dialog (I assume you use the rte to write your newsletter) and then replace this placeholder in a custom hook (search for contentPostProc-all). There you can read your typoscript config or from any other place (own db table, csv, whatever).
You may also use the browse link dialog hook to add your custom links. Take what fits best for you.