pageStart Portal issue

Elements Component Development
1

I noticed that if there is more than one component using

@portal(pageStart, includeOnce: true)

that a newline character is sometimes (not always) being added at the end of each one. This looks neater in the page source but is breaking the HTTP header which may stop sessions and cookies working.

I have been careful to ensure I place the opening PHP tag immediately after the @portal and the closing PHP tag before the @endportal. It seems that Elements is sometimes (not always) adding the new line between one components closing tag and the next components opening tag.

<?php
code here
?> // Newline seems to be added here
<?php
code here
?>
2

I’ll add a ticket to investigate this, but if you could provide a full code example with expected output, that’d be a big help :folded_hands:

3

I made some more tests and found a pattern. If I have two or more components that use

@portal(pageStart, includeOnce: true)

with includeOnce set to true then I see the new line after the component. If I change the includeOnce on one of the components to false then the new line disappears. I hope that provdes a clue!

A connected issue happens in the ‘Edit Extra Code’ dialog for the page. If I type a single line of code in the Page Start section like this

Capto_Capture 2025-06-14_10-19-37_AM
Capto_Capture 2025-06-14_10-19-37_AM517×167 9.84 KB

then that seems to have a newline at the end of it when the page is published.

4

I’ve ticketed this one for us to investigate :slight_smile:

5

Hey @vibralogix, the first issue with new lines in @portal statements should be fixed in today’s release, version 1.0!

I have a fix for the second issue too, new lines in the page code area. This should be going out in the next release due in the next few days.

Cheers

1 Like
6

Hi Tom,

That’s fantastic. Wow V1.0 :grinning_face:

Cheers for that.

7

Hi Ben,

I just heard from Bart and it seems there may still be an issue with the rw.page.docRootPath.

He published a page with the folder set like this

c86967d4-3d8d-48c5-8444-83bc0512d80d-spark-clipboard.png
c86967d4-3d8d-48c5-8444-83bc0512d80d-spark-clipboard.png610×260 18.2 KB

and in the published page the path is being sent as

../../../../../

instead of

../../

Any idea what could cause that. Maybe I am using rw.page.docRootPath incorrectly? It seems to work fine on my tests here though. We are both using the latest Elements from Yesterday.

8

Oh that’s strange! I’m having trouble reproducing that here, any chance you could send over a project that reproduces the issue?

9

Hi Ben,

It is odd as the path seems to work ok for me too when I try didn’t folder levels. I am doing a full publish to my local folders rather than FTP that Bart is using but I don’t see why that would make any difference.

Here is a download link for his project. He tried to send it via the Elements Cloud but ‘I don’t know why, but since the latest build I can upload project to Elements Cloud, but they disappear in the list and I can’t copy a link’

https://www.dropbox.com/scl/fi/9hmoruau7rnckzg3u6nce/BAOW-25-26._2.0_elements.elements.zip?rlkey=3ivi1m4kcjh9h34whcyqmkku0&dl=1

An example problem page is in Bestuur - Pro League - JPL_01_inschrijvingen

Capto_Capture 2025-07-10_10-11-31_am.png
Capto_Capture 2025-07-10_10-11-31_am.png299×721 31.4 KB

Maybe I am not using rw.page.docRootPath correctly?

10

I’m wondering if you’re out of cloud storage as we haven’t coded a warning to alert the user about this yet :grimacing:

Can you check your cloud storage in the preferences, it’s under: Settings > Account and displayed in the bottom right hand corner…

11

I will double check with him about that. Let me know when you have the file downloaded from Dropbox.

12

Hi Tom,

I did some tests with Bart’s project here and when I export it is using the incorrect path of ../../../../../

I added a console.log to my component and it is showing the same ../../../../../ in Elements editor too. On my own projects it is always correct no matter if its one or two folder levels down.

In my componnent I have this at the top of hooks.js. Maybe I have something missing causing rw.page.docRootPath to be messed up?

const transformHook = (rw) => {
  const {
    slMembersOnly,
    slRegisterForm,
    slUpdateForm,
    slLoginRedirectForm,
    slLoginForm,
    slContactForm,
    slWhoHasAccess,
    slUsergroups,
    slUsernames,
    slAllowPublic,
    slAllowExpired,
    slCustomPath,
    slForceDBRead,
    slblabMemberProfilepage

  } = rw.props;
  console.log(rw.page.docRootPath);
13

Hi @tpbradley,

Just wondered if you had a chance to look at the odd paths in the project when publishing?

Thanks Adrian

14

Sorry @vibralogix,

I was sidetracked with the recent Elements and Classic releases. I have the sample project from Dropbox and will take a look at this today!

Cheers

15

No problem I know you have been busy these days