For lack of a better Status, I have closed as duplicate and this should be handled by the related issue, which I just applied.
Thanks all.
Cheers,
Andrew
Done and DONE!
Thanks Dale. Applied to DEV and will tag a new release shortly.
Cheers,
Andrew
@jayvolk, I tested my suggestion that you just create a normal email web handler using the WebForm Settings UI and it does indeed work.
I think this can be closed as works as designed.
Cheers,
Andrew
I think you will need to use the "public" file system for uploading files and images. I am using it for this and it is working when I switch my form to upload the files to the public file system.
I haven't used this module yet but I have built similar webform_to_node modules that create a node based on webform submissions and providing that this module works, you would simply add a webform handler as an email so that when the form is submitted, the appropriate email is sent.
Cheers,
Andrew
Executive decision.
I added the patch and committed to DEV.
I'll tag a new release after I tackle a couple of other items.
Cheers,
Andrew
Hi Chris,
Sorry this issue has languished without any remarks or comments.
I'm not sure that it matters any more for your needs but, BASIC was designed to allow the theme developer to have a stripped down theme that they could add whatever was necessary to. In your case, you would add a template for views tables and then you could add whatever twig markup you needed to insert classes into the columns. Then of course you'd have all of the control you'd need.
I'm going to close this issue as works as designed.
Cheers,
Andrew
This is related to issue:
Primary/Secondary Menu Regions (2901386)
I'm going to leave it as postponed until we decide on that one. If we do choose to go ahead with the related issue, then #navigation css will be valid.
Cheers,
Andrew
I think this is a good idea.
I've changed this to 3.x-dev and assigned it to me and added a patch. I'll leave it for review but I'll probably commit and push sooner rather than later because I always add these to my body classes.
Cheers,
Andrew
Cool. We can leave this on the back burner.
I'm doing a bunch of Drupal development so I will give those a look and see how they fit. I haven't used browser synch for a long time but I recall it being pretty useful at times.
Cheers,
Andrew
I'm closing with "works as designed".
If you have content in a sidebar it will show, if not. It won't. I'm not sure what the reference to 404 pages is.
Feel free to reopen if you have more info to add.
Cheers,
Andrew
We no longer have Browser-Sync in BASIC so I'm going to close this issue.
I'll create another issue to remove or reintegrate browser-sync in BASIC because the settings for Browser Sync still exist in Themes/Settings/Basic
Cheers,
Andrew
Oops... ignore patch on #6.
I forgot to edit info.yml to make it aware of the change to add the regions. Use patch #7.
Cheers,
Andrew
Patch to include main and secondary regions
On further reflection, I see @dale42's point about using the primary & secondary regions. I've rolled it out in a clean site with the 3.x version and it works well. I'm leaning towards re-rolling the patch for version 3.x for this approach.
Cheers,
Andrew
I tend to agree with the idea of just removing that block of twig because it is redundant.
I'll leave this open in case anyone following cares to comment and in the next couple of days I'll remove the redundant twig code and push to dev.
Cheers,
Andrew
I'm closing all of the old and outdated issues. This one appears to be an edge case which isn't relevant for version 3.0.
Cheers,
Andrew
Closed as outdated.
Cheers,
Andrew
Sadly, the installer is no longer possible with BASIC theme so I'm closing this issue.
Cheers,
Andrew
@criscom, I'm closing this as outdated as I don't think it is an issue with today's Drupal and the 3.x version of BASIC. Please reopen if that is not the case.
Cheers,
Andrew
Per @leahtard's comment, this is how BASIC theme works so I'm closing with works as designed.
Cheers,
Andrew
I'm closing this as outdated.
I'm going to close this as outdated.
This is no longer an issue and was handled in https://www.drupal.org/project/basic/issues/3318614 🐛 Maintain some padding around the content. RTBC
Cheers,
Andew
I'm going to close this as works as designed because it's so old and likely no longer relevant.
You'll build your own css for lists in the base/_lists.scss file.
Cheers,
Andrew
Hi Guys,
I've tinkered with this over the years and it seems we no longer package the install script so I'm going to close this issue. If someone can come up with a plan to reintegrate an installer into BASIC, please open a new issue and we can build that out.
Cheers,
Andrew
I'm going to close this as can't reproduce which is largely in part because it is such an old issue that it has become a non-issue. If you still find that this behaviour is present in the current version (3.x) then reopen the issue and we'll see if we can resolve it.
Thanks,
Andrew
IE is no longer supported and this is the 8.x version which is also no longer supported so I'm going to close this issue.
Thanks for the interest and activity.
Cheers,
Andrew
Closed outdated
Fixed. Thanks.
Have pushed to DEV and will tag a new release with it in the near future.
Patch
I've changed the title and version of BASIC to better address the issue.
I've used both Yarn and NPM to install BASIC. I think Yarn does as good or better a job at installing BASIC and Yarn can be used to run the watch:all script that is defined in the package.json file.
I've found that NPM can be problematic on MACOS when you upgrade from one major version of MACOS to the next because the Developer Tools are sometimes behind in support for Node libraries and requirements so YARN is a good option. I think we should have both. I'll update the README and commit that to the DEV.
Cheers,
Andrew
I'm doing some light housekeeping in the issue queue and I'm going to close this and the related issue as outdated. I'll add a note to the roadmap to see if there's any interest in bundling a responsive drop down menu but it seems to me that Drupal Dev's have their own favourite menu systems and will drop them in rather than wrangle something built in.
Cheers,
Andrew
I'm doing some light housekeeping in the issue queue and I'm going to close this and the related issue as outdated. I'll add a note to the roadmap to see if there's any interest in bundling a responsive drop down menu but it seems to me that Drupal Dev's have their own favourite menu systems and will drop them in rather than wrangle something built in.
Cheers,
Andrew
Hey Mark,
I'm closing this ancient issue as outdated. I loved that installer (I think you wrote it IIRC) but drush and Drupal broke it.
Cheers,
Andrew
Cool idea of demoing BASIC Theme.
I added a paragraph on the project page to describe how to spin it up at Simplytest.me.
I'm marking this as fixed.
Cheers,
Andrew
I'm closing this as outdated because Drupal 7 is no more.
Cheers,
Andrew
Thanks for all the work on this back in the day.
I'm closing this as outdated because Drupal 7 is no more.
Cheers,
Andrew
Fixed and committed to the 3.x-DEV branch. It'll be in the next release.
Thanks again.
Cheers,
Andrew
Thanks for this issue.
It's been one of my frustrations as well but I have never thought to tackle it until now.
I've moved this to the 3.x-dev version and I've borrowed from the Olivero theme to fix this. Patch is attached and a screenshot of the results. I'll be committing this to the DEV release shortly.
Cheers,
Andrew
I'm going to close this as won' fix.
I spent some time in 2019 trying to resurrect the install script and ran into road blocks. If someone else wants to resurrect it feel free to reopen this issue or create a new one.
Closed as this is/was outdated several years ago.
Thanks guys,
I've pushed this to the DEV and it will be tagged in the next release.
Cheers,
Andrew
After some review, I've decided to approach this issue in a different manner than introducing a rule that applies 1% padding to all div containers. I've attached a patch that achieves the same goal but with additions that are more in line with existing css rules in the theme. I'll commit this to DEV shortly.
I don't think this is an issue. BASIC is simply a framework and it's up to the front end developer to decide how they are going to render the menu. Therefore, they will be adjusting the /sass/components/_navigation.scss files to do so. I'm closing this as works as designed.
Cheers,
Andrew
Closed duplicate and resolved in 3.x release.
Committed and pushed to DEV
I'm going to close this issue and have created a new one on version 3.x. I've duplicated the improvements to the UX using the work that was done by @Abhay Sharma on issue and will credit accordingly.
Cheers,
Andrew
Patch from @ Abhay Sharma on issue: https://www.drupal.org/project/basic/issues/3361383 🐛 Spacing issues on the page components RTBC
Cleaning up the issue queue
Thanks @arti_parmar
Your patch has been committed to the DEV release and I'll tag a new alpha release shortly.
Cheers,
Andrew
Thanks again Paul.
Patched and committed.
Cheers,
Andrew
Thanks @arti_parmar,
I've committed the patch and will tag a new release once I have reviewed and committed other outstanding RTBC issues.
Cheers,
Andrew
Hi Paul,
Sorry for the late reply.
The answer is yes. BASIC will be supported through Drupal 11. I'll be reviewing and committing RTBC issues and making sure that it is D11 capable.
Cheers,
Andrew
Also ran into this issue today.
Two days ago, we updated from the LinkIt version 6.1.6 to LinkIt version 7.0.5 and I was not certain if that was the reason for the Insert button hiding the IMCE file manager icon.
As a workaround until this is resolved officially, I have added the following rule to my theme CKEditor stylesheet:
.ck.ck-labeled-field-view.ck-labeled-field-view_full-width {
padding-right: 1rem;
}
Cheers,
Andrew
The patch works as expected.
I'm bumping this to reviewed and tested.
Cheers,
Andrew
I applied the patch and it worked but in Drupal 11 there is a fatal error when attempting to access the settings form. I am just looking at how to resolve the problem.
I have switched to needs work and will update with a patch if I am able to resolve the problem
The patch in #2 works and there is no reason why it shouldn't be applied and released.
I changed this to "critical" because without this patch there is no way to get to the webform handler if a webform confirmation file handler has been attached to the form.
I found a method of removing the Geonames API username and reseting it to use whatever default username it uses. I went to Extend -> Uninstall Module and removed all of the entities that had been created without uninstalling the weather module. Then I navigated to the UI Settings for Weather. I made certain that it was not using a Geonames API Username. I created a new display, added a place and then placed it in Structure -> Blocks -> Block Layout. Now I get the forecast for today GMT.
@lobsterr, fair enough and thanks for closing the issue so that it's not just hanging.
The method I proposed using BBE like markup ( #4 ✨ HTML break tag in menu link Active ) has been useful in websites I've built for universities and associations where menu links need this type of treatment for visual context. Rather than try to mess with Superfish core, I added a custom module to override Superfish to use my tokens when rendering the menu. If I have the bandwidth, I'll release a module or I'll add to the docs so that others can work around it.
Cheers,
Andrew
It appears that once the Weather module uses a valid Geonames API username, there is no way in the short term to get back to using no Geonames API username and it seems to be stuck on providing a forecast 72 hours in the future. I am still investigating how forecast.formatted_date is derived.
awasson → created an issue.
awasson → created an issue.
@dan612, I'm so sorry to hear that. It was a really great project while it was working. I modded it a few times to keep it working as I migrated some very large sites but then I had to abandon it and run migrations the old fashioned way because it was breaking everything.
It must be a caching issue. I'm using Chrome primarily but I also use FF and Edge and it appears normal. I'm on Mac OS. Perhaps there is an issue with Windows/Chrome but I haven't been made aware of it by any of my clients who are on Windows and use Chrome.
@stevenpatz, I have the same versions of Drupal and IMCE as you and it is working correctly on mine. Did you disable image uploads in Configuration -> Content Authoring -> Text Formats and Editors ? Under image, enable image uploads should be unchecked.
Experiencing the same issue on a Drupal 10 site.
#20 has fixed the issue
No loop problem detected yet.
I can affirm that this is an issue that occurred between core versions Drupal 10.3 and Drupal 10.4.
Every one of my Drupal sites that were updated to Drupal 10.4 have lost the ability to access the IMCE file manager from the Core CKEditor image tool.
I don't see any errors in the Javascript console or the error database and the CKEditor has been set for Images not to use the upload feature in Core which should enable IMCE to work with it. Something must have been changed in core to disable IMCE integration.
Cheers,
Andrew
Hi Bryan,
The CiviCRM Entity module devs have indicated that it's unlikely I'll be able to resolve this issue without custom coding my own Views field plugins so I'm going to close this as works as designed and carry on.
It's a very cool module though so I'll be using in again when I can. I may poke around and see if I can add a custom views field that works in tandem with it where I can override the database connection to assign the one for CiviCRM. I think that would work but it would probably be easier to just write a purpose built plugin for this one specific job. I've got Views field plugin boiler plate code I can borrow from a recent project that did something similar with a remote data warehouse.
Thanks again for the help.
Cheers,
Andrew
Hi Bryan,
Yes, both databases are on the same server which is pretty standard for the Drupal/CiviCRM sites that I maintain. CiviCRM entities are made available to Drupal via a CiviCRM Entities module.
I've been developing in CiviCRM since Drupal 6 and prior to Drupal 9/10 we used to add a hard coded DB array to the settings.php file to tell Views about the CiviCRM database. It was the form of:
$databases['default']['default']['prefix']= [
'default' => '',
'civicrm_acl' => '`database_civicrm`.',
'civicrm_acl_cache' => '`database_civicrm`.',
'civicrm_acl_contact_cache' => '`database_civicrm`.',
'civicrm_acl_entity_role' => '`database_civicrm`.',
. . . More definitions . . .,
];
I've opened up a conversation of the mattermost channel that handles the CiviCRM Entities module to see if there is a database api method that recognizes the database that is responsible for the appropriate entities.
The actual error I get is as follows:
SQLSTATE[42S02]: Base table or view not found: 1146 Table 'database_civicrm.civicrm_event' doesn't exist: SELECT node_field_data.nid AS "nid", NULL AS "civicrm_event_start_date", NULL AS "id", :view_combined_event_listing_block_1_combined_event_listing_block_1 AS "_view_id", NULL AS "_order_0" FROM "node_field_data" "node_field_data" WHERE ("node_field_data"."status" = :db_condition_placeholder_0) AND ("node_field_data"."type" IN (:db_condition_placeholder_1)) UNION SELECT node_field_data.nid AS "nid", NULL AS "civicrm_event_start_date", NULL AS "id", :view_drupal_event_listing_default_drupal_event_listing_default AS "_view_id", NULL AS "_order_0" FROM "node_field_data" "node_field_data" WHERE ("node_field_data"."status" = :db_condition_placeholder_2) AND ("node_field_data"."type" IN (:db_condition_placeholder_3)) UNION SELECT NULL AS "nid", civicrm_event.start_date AS "civicrm_event_start_date", civicrm_event.id AS "id", :view_events_listing_default_events_listing_default AS "_view_id", civicrm_event.start_date AS "_order_0" FROM "civicrm_event" "civicrm_event" WHERE (("civicrm_event"."is_active" = :db_condition_placeholder_4) AND ("civicrm_event"."is_public" = :db_condition_placeholder_5)) AND (((DATE_FORMAT((civicrm_event.start_date + INTERVAL -25200 SECOND), '%Y-%m-%d\T%H:%i:%s') >= DATE_FORMAT(('2024-12-10T07:00:00' + INTERVAL -25200 SECOND), '%Y-%m-%d\T%H:%i:%s'))) OR ((DATE_FORMAT((civicrm_event.end_date + INTERVAL -25200 SECOND), '%Y-%m-%d\T%H:%i:%s') >= DATE_FORMAT(('2024-12-10T07:00:00' + INTERVAL -25200 SECOND), '%Y-%m-%d\T%H:%i:%s')))) ORDER BY "_order_0" ASC LIMIT 11 OFFSET 0; Array ( [:db_condition_placeholder_0] => 1 [:db_condition_placeholder_1] => drupal_event [:view_combined_event_listing_block_1_combined_event_listing_block_1] => combined_event_listing:block_1 [:db_condition_placeholder_2] => 1 [:db_condition_placeholder_3] => drupal_event [:view_drupal_event_listing_default_drupal_event_listing_default] => drupal_event_listing:default [:db_condition_placeholder_4] => 1 [:db_condition_placeholder_5] => 1 [:view_events_listing_default_events_listing_default] => events_listing:default )
If I can't find a solution that uses the database API, I'll likely just write a module and run the queries in code. Hopefully I can though because this would make a lot of Drupal/CiviCRM listings better; not just events but newsletters and other things that would benefit from being listed together.
Cheers,
Andrew
awasson → created an issue.
I have also been struggling with this issue on my Full HMTM editing profile. My Basic HTML is fine.
It happened after upgrading to CKEditor 5 in Drupal 10 from CKEditor 4 in Drupal 9.
For me, this involved upgrading the Anchor Link module from CKEditor 4 to a CKEditor 5 version.
I found that the library for Anchor link was not loading and throwing an error that basically crashed the JS interpreter and stopped all of the other JS from running. I would check to make sure that any additional plugins that your using on the text editing profile that is causing issues are not having conflicts.
Cheers,
Andrew
I just realized, I should change this to Needs Review.
Cheers,
Andrew
@thorsch, Unfortunately, I've had to move on and am migrating the long-hand way with drush migrate tools.
Acquia Migrate: Accelerate really looked great when it arrived last year but now, it seems to me that there are two issues:
1) Drupal 9 modules that Acquia Migrate: Accelerate tries to map to the Drupal 7 modules in the source site are no longer available via composer.
2) Something in Context changed to make Acquia Migrate: Accelerate delete 90% of my site.
Beyond that, none of the maintainers seem to be paying attention to the issue queue. I maintain a couple of much less complex Drupal modules, so I understand the overhead of the issue queue but I can't wait so I've moved on. DrupalCon is in December this year so maybe there will be some announcements. If you can wait, it might be worthwhile.
In the meantime, there is another module to look at: https://www.drupal.org/project/migrate_wizard →
Cheers,
Andrew
awasson → created an issue.
Sounds like a good plan.
I'll add that to my todo list.
Fixed. Will be on the next release.