Yes⊠just update to the latest version of Elements and youâll be good to go!
All good to go. I couldnât see the missing bit until I changed over so apologies. WELL DONE EVERYONE!!
1 Like
Fatal error: Uncaught Twig\Error\RuntimeError: Impossible to access an attribute (âimageâ) on a null variable in â__string_template__8eefe04f17755e02690e44254c006dd7â at line 7.
+ loads of other lines of errors
get this error , downloaded project, opened each page individually in the browser, when viewing the Author page it throws this error
I think youâre probably trying to preview the Author page directly â so clicking the preview in browser icon in Elements. Correct?
If so, you will see this error as the Author page has no âitemâ to load. If you view the author page via a linked author name, then it will correctly load the author data and the error should be resolved.
I know these errors could be better handled â weâll improve on this going forward 
1 Like
same with the Post page â it doesnât have a post item to load, so currently displays an error if previewed directly.
View the post page by clicking on a post title on the homepage and itâll work as expected.
1 Like
Thanks understand now
@dan any chance you could change the project to a link saves me copying and pasting dl 3 times now thanks
first bug.
I always use the option in Elements to assign the URL slugs myself. But when I enter /blog/ in the Folder field, I always get this error message.
However, if I remove the path, everything works.
When I run Elements CMS locally, all of my projects work fine. However, as soon as I publish my projects with the CMS online, I always get an âHTTP ERROR 500â for /blog/.
I even uploaded the test file for troubleshooting. Is anyone else experiencing the same problem?
test with php. version 8.3 and 8.4.
Try not to enter the â/blog/â for the folder name, leave out the â/../â, just âblogâ. I have never had to do that with Elements, and it works fine.
Now we are in for some fun! Made my day when I saw this. Lots of testing and experimenting coming up. Stoked to finally get my hands on the CMS. Congratulations.
1 Like
Wonât there be an index.html and an index.php in the same root folder without a blog folder (without / /) ?
Iâll investigate this one further tomorrow!
Sorry, some of my text inexplicably went missing, I have added it back. Yes, there needs to be a folder name, and yes, it should not have slashes in it.
1 Like
@ben NOT A BUG - on the âAUTHORâ tab on the author page it shows three authors, if you want to add more in content bar on right side there is a heading âCOLUMNS and ROWSâ but there are no rows only columns to add. So how do I get 6 authors to show without making them micro size? TIA
@ben I tried a simple test to see if I could get going with the CMS, and clearly, I must be doing something wrong.
What I have is an existing page that I want to add a title and some text to the top of the page. I add a container, inside the container I add a CMS Item, inside the item I add a text component for the title (with the Twig {{item.title}}). I also added a typography component inside the item and pointed it to {{item.body}}.
In my project, I created a folder called âcmsâ with a folder called âcontentâ inside of it that contains a single Markdown file called âprivacy-policy.mdâ.
I then hooked up the CMS item to the markdown file in the project.
Then I tried to preview the page, and this is what I get.
What am I doing wrong as this seemed to be so simple?
That looks like your page might not be .php. Can you confirm if the page is .php rather than.html?
Of course, I did not have the page set to be PHP. Once I did that, it worked perfectly.
Be nice if there were some sort of warning when using the CMS if you forget to change the page to PHP.
1 Like
Would be a handy feature
