In the past, double clicking in the text component would then enable editing in the text component.
In Beta 22, if you double click in an empty portion of the component, nothing happens. If you double click on text in the text component then it works and you can edit the text.
On another note, Select All, Copy, and Paste are all working again, but Shift-Click is not. Shift-Click exits editing and selects the Text Component itself
Hi @dan
I’m also seeing on the @Text component, when assigning a link, the pageId is not showing the correct page path, looks like it is still using the original default page name, instead of what was set on the page in it’s Folder & Filename.
I’ve just noticed in your test project that you’re extracting and logging the mytext property in the hooks file. These values use an internal type and should not be processed in any way. The format can and most likely will change over time.
There are two supported ways to obtain a valid link to another page/resource. Using a link property, or, as Dan said, using the rw.pages property in the hooks file.
Change is fine, as a matter of fact here’s a good change, you already pull anchor when setting a link property, just give us the relative url and be done with it. There’s no way in your api for us to get that link, you guys have to provide that.
I’m not entirely sure what you’re trying to achieve here — could you provide a sample project or a more detailed explanation of where/how you would like to access relative URL?
It would really help me if you could describe the exact issue you’re encountering. With more context, I’d be happy to explore potential solutions or suggest an alternative approach.