-
-
Notifications
You must be signed in to change notification settings - Fork 817
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CiviCRM Standalone: base classes #22227
Conversation
(Standard links)
|
I created a repo here to help get started, and also has the Edit: repo link: https://github.com/mlutfy/civicrm-standalone Doc updated here: https://lab.civicrm.org/dev/core/-/wikis/standalone |
88176a3
to
6fdd01f
Compare
odd, I don't think the test fail relates?
|
It's a timing rollover - known issue - note 1639081466_168 vs 1639081467_168. It's a little hard to fix because it would touch on a previous security fix. |
By the way where is the "repo" you mention above? |
Here's the repo: https://github.com/mlutfy/civicrm-standalone |
jenkins, test this please |
1 similar comment
jenkins, test this please |
*/ | ||
public function getLoginURL($destination = '') { | ||
$query = $destination ? ['destination' => $destination] : []; | ||
return \Drupal\Core\Url::fromRoute('user.login', [], ['query' => $query])->toString(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This comes up as a fatal error on an entityref field if you choose e.g. the New Individual popup. Maybe for now it could be return CRM_Utils_System::url('civicrm/todo/user/login', 'reset=1');
or something like that, just so the popup works.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@demeritcowboy Thanks - I updated to civicrm/user/login
, since I think that makes sense as a login URL.
Jenkins re test this please |
Diving back into this is hard. I had forgotten that the installer now works, but I had not committed the file. Example: after entering DB credentials: However, there are shenanigans after installation - some path is not correctly set, so the menu and CSS are not loading correctly: ah - and because of my composer.lock on |
Fixed the linting warning. |
* Standalone specific stuff goes here. | ||
*/ | ||
class CRM_Utils_System_Standalone extends CRM_Utils_System_Base { | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see you've removed registerPathVars() in this latest update. It means that [cms.root]
is now null, which kind of makes sense here, but we'll need to hunt down where it's used since it generates errors. Or perhaps it should point to web
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hmm I have to admit I don't really recall. I grepped a bit in the codebase about cms.root
and it seems there more for convenience, for settings, but I'd be surprised if extensions used it? (there are better functions for generating URLs and getPaths)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think I took notes but it might have been during install. And I seem to remember something about the system settings - directories page (which would make sense there).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also I was using php 8 this time around, which is less forgiving. I didn't intend to, just it happened to be in my path from something else and then composer(👿) locked everything to php 8+ so it won't even run with a web server using 7.
jenkins, test this please |
Where is this at - to the extent that it only touches stuff within the standalone subsystem I think we can have a more 'work-in-progress' attitude - but if this is exposing it as available to install then I guess the concern is we might be offering something that we are not yet delivering. For background I think this has concept-approved in terms of 'we do want standalone to work' - so it's a question of how to support work on it without creating confusion |
I see pluses and minuses to merging. There's the ones you've mentioned, and then
After writing that out I see it leans a bit towards leaving here. But also for the concern about advertising it I don't see anything in here that makes it visible to users. I'm 50/50 personally. |
Personally, I'd favour merging, because the various decisions that will go into Standalone will be muddied if it's all behind a single PR. For example, |
🚀 |
Overview
As CiviCRM has evolved, and so has content management systems, and how organizations manage their CRM, it seems like a good time to bring CiviCRM Standalone back.
More information:
https://lab.civicrm.org/dev/core/-/wikis/standalone
Technical Details