I setup my ImpressCMS site using a Let's Encrypt SSL certificate. Everything works fine, nothing specific to configure other than putting 'https' in your root url. The site was running a bit sluggish, due to the server being on the other end of the world, so I decided to activate the free Cloudflare option my hosting company offered.
After that, once Cloudflare was up and running, my site was unreachable due to 'the site redirecting in an incorrect way'. Because the site has been working without issue before, I figured it was the cloudflare setup that needed adapting.
I found this article on the cloudflare support site that explains what was happening : my site was SSL-only, but the cloudflare default setting is for 'Flexible SSL'. The Flexible SSL option acts as a SSL proxy between your users and your site, and can be a good option if you don't have the opportunity to run your site with an SSL certificate, but you want to expose an SSL address to the world. Cloudflare then exposes a HTTPS address to the outside world, but communicates with your servers without it.
Changing the option from 'Flexible SSL' to 'Full SSL' immediately fixed the issue for me. Site response times have improved considerably since then.
As a follow-up on this, you could implement this using a OAuth2 server, where the OAuth2 server lets the user login in your ImpressCMS site, and then notify your other webapp that the user is verified. That means custom development on both sides, and i don't think that this has been attempted before for an ImpressCMS site.
This would be the most flexible solution, in the likes of logging in with Twitter, Google, Microsoft or Facebook into a site.
I totally agree with @skenow. This way you don't need to duplicate the login procedure in ImpressCMS, and you can still use the existing userbase.
So - you want to have your login be the login from your ImpressCMS site, with all their users and passwords, and the rest of the content be restricted, but not an icms site?
Then, each of your pages must check for a valid user, like your ICMS site does (icms::$user is set and meets your criteria).
To access this information, the easiest way I see is to require mainfile.php in all your pages, which will give you a connection to the db that holds the users and the salt key stored in the trust path to complete the authorization.
i would like to build a custom php application without using icms but i would like to use icms user/password from
user table to login to my system
is there any code script out there that i can use
In Impresscms everything is good, and needed I think.
But (and no critisism) there is this intrigueing Q about modules and page (blanks OR module-page) implementation.
page(empty or module) - block positions - theme-data - template manager - module(install area)
// many possible alternatives both for physical and visual connection.
... and where those should best be placed in admin area? For me as user (as publisher) this is much a topic wich make the site a mystery or comprehenceble.
This could perhaps be in a new thread.
I uncheck the Enable line break whenever I post using the WYSIWYG editors and the line breaks work appropriately then.
Initial post of this reply has the option checked (enabled)
The post displayed properly for me and this section was added with the box unchecked.
You think it is possible to code a "Theme manager" that is more adoptable to 2 or more page-themes? - - and some control-pointer in module-install module (or similar)? < - - .# - -> Is there any Bootstr. 3.3.7 (was it?) yet? <- - # - - > Being the most [easy cms/features] makes reputation // walked.
I noticed as well, and it is strange that you are having problems with line breaks and others (like me) don't. I see several possibilities : browser, os, user group. Or worse : a combination
I don't have the opportunity at the moment of testing this in the short term, so I appreciate any help on identifying the issue
BTW re. my problem with linebreaks: If I preview the post, or edit it after submission, it looks fine (linebreaks are ok). So it seems that the linebreaks are being stored correctly in the database, but they are being removed when the post is actually *viewed*.