Unable to edit content
Permalink
Hi Guys,
So this is my first time with Concrete5 and I'm still trying to figure this all out. I have made a layout myself and I am experimenting with integrating Concrete5 into it for CMS purposes. I have managed to link the css, js libraries and put the footer and header for concrete5 in. Now, when I log in and click to edit the areas I have created, the add content block jumps to the top of the page instead of offering the blocks and I am unable to actually select the editable area although the areas name does appear (not the areas highlightable border though).
Link:www.www.thedesignhammock.co.za/Metprep...
So this is my first time with Concrete5 and I'm still trying to figure this all out. I have made a layout myself and I am experimenting with integrating Concrete5 into it for CMS purposes. I have managed to link the css, js libraries and put the footer and header for concrete5 in. Now, when I log in and click to edit the areas I have created, the add content block jumps to the top of the page instead of offering the blocks and I am unable to actually select the editable area although the areas name does appear (not the areas highlightable border though).
Link:www.www.thedesignhammock.co.za/Metprep...
Aww shucks. I guess I will have to do some research then and see if I cant dig out all those little javascripts. Thanks! (on the plus side, the site is rendering and displaying as designed at least, even though it was a miniature nightmare linking all the files lol)
Ok so I had a look. Turns out, I had forgotten to re-correct the file path for museutils.js in the museconfig.js after I had been tinkering around. After fixing it, the website loads as per normal and displays correctly. My appologies for that. I ran chromes console to see whats kicking up errors and the following came up (see atached). Any ideas?
[All of those errors are originating from within concrete5's js libraries]
[All of those errors are originating from within concrete5's js libraries]
@InstaGraemie
The site still alerts on load.
The Muse scripts are likely conflicting with concrete5's scripts.
I also noticed that the site and the parent site are not responsive. This leads me to recommend that if you are interested in getting into web design, you will be well served in learning the HTML, CSS, and JavaScript to do it from scratch. The alternative is focusing on the design aspects and using a developer to turn them into a working site.
The site still alerts on load.
The Muse scripts are likely conflicting with concrete5's scripts.
I also noticed that the site and the parent site are not responsive. This leads me to recommend that if you are interested in getting into web design, you will be well served in learning the HTML, CSS, and JavaScript to do it from scratch. The alternative is focusing on the design aspects and using a developer to turn them into a working site.
Ok, so I've coded the websites content myself now using bootstrap and at first everything went well. That is until I connected up the bootstrap.css with the correct file path. It seems that the bootstrap.css on its own breaks the Concrete5 user interface when trying to edit a page. Any ideas?
(As a side note, I have successfully created and installed a page_theme.php file with the coding as seen below so I am pretty sure its not the js interfering now.)
page_theme.php code:
(As a side note, I have successfully created and installed a page_theme.php file with the coding as seen below so I am pretty sure its not the js interfering now.)
page_theme.php code:
<?php namespace Application\Theme\Metprep; use Concrete\Core\Page\Theme\Theme; class PageTheme extends Theme { protected $pThemeGridFrameworkHandle = 'bootstrap3'; public function registerAssets() { $this->providesAsset('javascript', 'bootstrap/*'); $this->providesAsset('css', 'bootstrap/*'); $this->providesAsset('css', 'blocks/form'); $this->providesAsset('css', 'core/frontend/*'); $this->requireAsset('javascript', 'jquery'); } }
@InstaGraemie
What is breaking in the user interface while editing?
Also, on your site, bootstrap.js is throwing an error because jquery is not loaded. This means there is an issue with assets.
What is the file path to your theme page_theme.php?
What is breaking in the user interface while editing?
Also, on your site, bootstrap.js is throwing an error because jquery is not loaded. This means there is an issue with assets.
What is the file path to your theme page_theme.php?
Thanks for the jQuery tip. I had been playing around with the page_theme.php and had forgot to change it back to prodivesAsset. the file path to the page_theme.php is:
www.www.thedesignhammock.co.za/Metprep/application/themes/Metprep/pa...
As for what exactly is breaking. The Header bar of Concrete5 is not visible when bootstrap.css is loaded. The white bar at the top with the add content, pages, etc. I have however noticed (only now when I incidentally loaded it on safari to test compatibility) that what I assume to be the footer (with the little admin button and the dropdown menu) is underneath the navbar. The only reason I noticed it at all is because safari and chrome must handle objects that are fixed to the browser top differently (safari pins to top with overflow of scrolling and chrome does not).
www.www.thedesignhammock.co.za/Metprep/application/themes/Metprep/pa...
As for what exactly is breaking. The Header bar of Concrete5 is not visible when bootstrap.css is loaded. The white bar at the top with the add content, pages, etc. I have however noticed (only now when I incidentally loaded it on safari to test compatibility) that what I assume to be the footer (with the little admin button and the dropdown menu) is underneath the navbar. The only reason I noticed it at all is because safari and chrome must handle objects that are fixed to the browser top differently (safari pins to top with overflow of scrolling and chrome does not).
Ahhhhhh, ok now I feel like such a paw paw. I just fiddled in chrome and found out that this entire time it was the damn z-index!!! The page wrapper it seems does not fix this problem. Shouldn't it? (I was under the impression the was supposed to stop that?) The div works fine for the side menu's but apparently not for the fixed navbar...
As it turns out though, If I hadn't been on this forum I never would have noticed the admin footer button underneath the menu which is still a problem. Why exactly is that happening? I have coded it with the usual just before the ending of the body tag and before the div close tag. Is this correct?
(sorry if these are really basic Concrete5 questions. I have noticed that it is NOTORIOUSLY difficult to find answers to such simple questions in the docs)
class="<?= $c->getPageWrapperClass() ?>
As it turns out though, If I hadn't been on this forum I never would have noticed the admin footer button underneath the menu which is still a problem. Why exactly is that happening? I have coded it with the usual
<?php Loader::element('footer_required') ?>
class="<?= $c->getPageWrapperClass() ?>
(sorry if these are really basic Concrete5 questions. I have noticed that it is NOTORIOUSLY difficult to find answers to such simple questions in the docs)
@InstaGraemie
The getPageWrapperClass() method and concrete5 interface CSS do not self-adjust for fixed headers. Theme developers have to adjust their themes to give the interface priority.
Here are two forum discussions on using a fixed header and several approaches:
http://www.concrete5.org/community/forums/customizing_c5/trying-to-...
http://www.concrete5.org/community/forums/customizing_c5/theme-fixe...
You mention that the admin footer button is underneath the menu. Can you take a screenshot of what you are describing, please.
The getPageWrapperClass() method and concrete5 interface CSS do not self-adjust for fixed headers. Theme developers have to adjust their themes to give the interface priority.
Here are two forum discussions on using a fixed header and several approaches:
http://www.concrete5.org/community/forums/customizing_c5/trying-to-...
http://www.concrete5.org/community/forums/customizing_c5/theme-fixe...
You mention that the admin footer button is underneath the menu. Can you take a screenshot of what you are describing, please.
Heres your screenshot. note the top right. (see Permalink)
I have also since fixed the navbar problem. I found a solution somewhere (cant remember where on the forums but anyways)
Something else came up though which I have not been able to correct. I have started setting up the CMS but I have noticed that I am unable to upload images directly due to file size limit (which coincidentally does not correspond to what my ISP has set [Concrete5 limit:2mb IPS limit:20mb]) nor via the incoming FTP method. Whenever I try (Incoming FTP method) I get an error message saying class finfo not found. did some digging and is also related to servers php but not really sure about that one...
I have also since fixed the navbar problem. I found a solution somewhere (cant remember where on the forums but anyways)
Something else came up though which I have not been able to correct. I have started setting up the CMS but I have noticed that I am unable to upload images directly due to file size limit (which coincidentally does not correspond to what my ISP has set [Concrete5 limit:2mb IPS limit:20mb]) nor via the incoming FTP method. Whenever I try (Incoming FTP method) I get an error message saying class finfo not found. did some digging and is also related to servers php but not really sure about that one...
@InstaGraemie
I am afraid I can't tell what is affecting that admin button from the screenshot. I would review your CSS, removing bits of it at a time to see what is causing the issue.
The setting you are looking for is "upload_max_filesize" and that can be found in your server php.ini.
Regarding the finfo warning, that is something you should contact your web host about.
Also, I noticed in your index.css, your CSS is not scoped/namespaced. The Greedy Styles section of the documentation explains why you should namespace your CSS to the "ccm-page" class to prevent overriding the theme's CSS.
https://documentation.concrete5.org/developers/designing-for-concret...
I am afraid I can't tell what is affecting that admin button from the screenshot. I would review your CSS, removing bits of it at a time to see what is causing the issue.
The setting you are looking for is "upload_max_filesize" and that can be found in your server php.ini.
Regarding the finfo warning, that is something you should contact your web host about.
Also, I noticed in your index.css, your CSS is not scoped/namespaced. The Greedy Styles section of the documentation explains why you should namespace your CSS to the "ccm-page" class to prevent overriding the theme's CSS.
https://documentation.concrete5.org/developers/designing-for-concret...
The site you linked to displays an alert message about missing files and does not render correctly.
Are you trying to combine a site created with Adobe Muse with concrete5? If so, I don't recommend it. The reason for this is that Muse likely has specific JavaScript files that may not work with, or break, the concrete5 interface and the HTML/CSS it creates will likely do the same.