# Beta 22 - Text Component Issue **URL:** \ **Category:** Elements\ **Created:** [November 28, 2024, 4:24pm UTC](https://forums.realmacsoftware.com/t/beta-22-text-component-issue/45446 "2024-11-28T16:24:00Z")\ **Posts on this page:** 13\ **Page:** 1
**Author:** ![sbchasin](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/sbchasin/32/26943_2.png) [@sbchasin](https://forums.realmacsoftware.com/u/sbchasin)\ **Post date:** [November 28, 2024, 4:24pm UTC](https://forums.realmacsoftware.com/t/beta-22-text-component-issue/45446/1 "2024-11-28T16:24:00Z")
@dan 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 ---
**Author:** ![Bill](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/bill/32/107_2.png) [@Bill](https://forums.realmacsoftware.com/u/Bill)\ **Post date:** [December 1, 2024, 8:54pm UTC](https://forums.realmacsoftware.com/t/beta-22-text-component-issue/45446/2 "2024-12-01T20:54:54Z")
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. ---
**Author:** ![dan](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/dan/32/28516_2.png) [@dan](https://forums.realmacsoftware.com/u/dan)\ **Post date:** [December 1, 2024, 9:37pm UTC](https://forums.realmacsoftware.com/t/beta-22-text-component-issue/45446/3 "2024-12-01T21:37:45Z")
Hmm, I’m not seeing that here 🤔 Can you share a sample project that shows the issue? (will make it much quicker to fix) ---
**Author:** ![Bill](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/bill/32/107_2.png) [@Bill](https://forums.realmacsoftware.com/u/Bill)\ **Post date:** [December 1, 2024, 11:49pm UTC](https://forums.realmacsoftware.com/t/beta-22-text-component-issue/45446/4 "2024-12-01T23:49:46Z")
Here’s a file, look in the Debug log and pageID: [File Link](elementsapp://downloadDocument/womN52zkhIWW) Here’s a screenshot, just in case: ![pageID_notupdating](https://europe1.discourse-cdn.com/flex005/uploads/realmacsoftware1/original/3X/a/a/aa3ed548a5a7871834cceeb74c4e4b8c0b04597a.png) If PageID isn’t a url, then we definitely need a url attribute in there for the link 😉 Thanks. ---
**Author:** ![dan](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/dan/32/28516_2.png) [@dan](https://forums.realmacsoftware.com/u/dan)\ **Post date:** [December 2, 2024, 9:54am UTC](https://forums.realmacsoftware.com/t/beta-22-text-component-issue/45446/5 "2024-12-02T09:54:23Z")
No bug here. That’s the unique ID for the page you’re linking too, not the actual url/link. **UPDATE:** btw. You can get any page properties you need, take a look at the “Page” custom component to get you started. Also See; [rw.page Docs](https://docs.realmacsoftware.com/elements-docs/elements-language/hooks.js/available-data/rw.page). ![CleanShot 2024-12-02 at 9 .56.29@2x](https://europe1.discourse-cdn.com/flex005/uploads/realmacsoftware1/original/3X/1/4/146ebcb6e7c9983db51763df8c7abfe9f985d878.jpeg) ---
**Author:** ![tpbradley](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/tpbradley/32/25503_2.png) [@tpbradley](https://forums.realmacsoftware.com/u/tpbradley)\ **Post date:** [December 2, 2024, 10:13am UTC](https://forums.realmacsoftware.com/t/beta-22-text-component-issue/45446/6 "2024-12-02T10:13:12Z")
Hi @Bill, 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. Cheers ---
**Author:** ![Bill](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/bill/32/107_2.png) [@Bill](https://forums.realmacsoftware.com/u/Bill)\ **Post date:** [December 3, 2024, 2:41am UTC](https://forums.realmacsoftware.com/t/beta-22-text-component-issue/45446/7 "2024-12-03T02:41:32Z")
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. ---
**Author:** ![tpbradley](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/tpbradley/32/25503_2.png) [@tpbradley](https://forums.realmacsoftware.com/u/tpbradley)\ **Post date:** [December 3, 2024, 4:42pm UTC](https://forums.realmacsoftware.com/t/beta-22-text-component-issue/45446/8 "2024-12-03T16:42:11Z")
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. ---
**Author:** ![Bill](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/bill/32/107_2.png) [@Bill](https://forums.realmacsoftware.com/u/Bill)\ **Post date:** [December 3, 2024, 7:42pm UTC](https://forums.realmacsoftware.com/t/beta-22-text-component-issue/45446/9 "2024-12-03T19:42:34Z")
@tpbradley It’s very simple, when someone is using the @text and sets a Link using the ‘Page’ selection, I need the relative path from the current page to the page that is selected, easiest to put it in a property inside of link, where my screenshot above shows. ![page_link_in@text](https://europe1.discourse-cdn.com/flex005/uploads/realmacsoftware1/original/3X/c/1/c159ae7f1ba4c3c280a2c8e6629b01f686df2fc3.png) ---
**Author:** ![dan](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/dan/32/28516_2.png) [@dan](https://forums.realmacsoftware.com/u/dan)\ **Post date:** [December 3, 2024, 8:09pm UTC](https://forums.realmacsoftware.com/t/beta-22-text-component-issue/45446/10 "2024-12-03T20:09:29Z")
Th real question is… why are you trying to extract a link from a @text block? ---
**Author:** ![Bill](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/bill/32/107_2.png) [@Bill](https://forums.realmacsoftware.com/u/Bill)\ **Post date:** [December 3, 2024, 11:35pm UTC](https://forums.realmacsoftware.com/t/beta-22-text-component-issue/45446/11 "2024-12-03T23:35:12Z")
Shhhhhhh… It’s a secret 🙊   I think I have a solution figured out 🥳 ---
**Author:** ![tpbradley](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/tpbradley/32/25503_2.png) [@tpbradley](https://forums.realmacsoftware.com/u/tpbradley)\ **Post date:** [December 4, 2024, 3:23pm UTC](https://forums.realmacsoftware.com/t/beta-22-text-component-issue/45446/12 "2024-12-04T15:23:07Z")
Hi Bill, I appreciate you’d like to keep things under wrap while you’re working on it. However, I feel I should again highlight that parsing the raw data from `@text` or `@typography` within the hooks file is not supported or allowed. If a component is found to be doing this I’m afraid it won’t be allowed onto the store for distribution. The reason for this is quite simple. In the future (possibly years down the line) I can almost guarantee that the text data structure will change. Any add-ons parsing the current data format will almost certainly break leaving us with a lot of unhappy customers. This has happened time and time again with RapidWeaver Classic where developers have used undocumented API’s. We really want to avoid this as it’s detrimental to users, developers and the platform as a whole. We’ve started to put together some guildlines for building add-ons, you can find it here > **[Add-on Guidelines | RapidWeaver Elements Docs](https://docs.realmacsoftware.com/elements-docs/elements-store/add-on-guidelines)** > > A guide to making sure your add-ons meets user expectations That said, I’m excited to see what you’re cooking up. If you do need to parse the raw text data for any reason, please tell us your use case. You can message us privately if you prefer. Cheers Tom ---
**Author:** ![Flash](https://avatars.discourse-cdn.com/v4/letter/f/f475e1/32.png) [@Flash](https://forums.realmacsoftware.com/u/Flash)\ **Post date:** [December 4, 2024, 3:43pm UTC](https://forums.realmacsoftware.com/t/beta-22-text-component-issue/45446/13 "2024-12-04T15:43:43Z")
> [@tpbradley](#): > > This has happened time and time again with RapidWeaver Classic where developers have used undocumented API’s. We really want to avoid this as it’s detrimental to users, developers and the platform as a whole. This! The forums were filled with these types of issues. The better solution is to use the tools provided OR in confidentiality, request a need that can be addressed in the proper API. I fully support this.