Drupal.org Feed
Clustering by node type on results page
Forgive me if I haven't found the right place to bring this up yet but...
Using core search and a theming layer solution, I've been grouping search results by node type.
This offers a nice way to quickly scan what types of results are available and get just the resources needed, when traditional results are less clear on this. It also can give weight to types and implemented in collapsable fieldsets, it's rather nice. This required a hack to increase the # of results (not a huge core hack.)
It certainly wasn't perfect, since you can't control the number of results in each cluster and pagers create a problem (so we set the number all the way to 100.)
Anyhow...
Looking to now implement facet clustering on the initial results page as we're moving to SOLR.
I imagine this could be done with SOLR views, but wondered if it might be facet territory rather than custom building it.
Thoughts about where to take the discussion are certainly welcome!
Clustering by node type on results page
Forgive me if I haven't found the right place to bring this up yet but...
Using core search and a theming layer solution, I've been grouping search results by node type.
This offers a nice way to quickly scan what types of results are available and get just the resources needed, when traditional results are less clear on this. It also can give weight to types and implemented in collapsable fieldsets, it's rather nice. This required a hack to increase the # of results (not a huge core hack.)
It certainly wasn't perfect, since you can't control the number of results in each cluster and pagers create a problem (so we set the number all the way to 100.)
Anyhow...
Looking to now implement facet clustering on the initial results page as we're moving to SOLR.
I imagine this could be done with SOLR views, but wondered if it might be facet territory rather than custom building it.
Thoughts about where to take the discussion are certainly welcome!
Documentation missing; broken external links
The links to the documentation on the project page are broken.
Required Nginx Modules
Upload Progress Module
http://github.com/masterzen/nginx-upload-progress-module
Read documentation
http://github.com/smoothify/filefield_nginx_progress/raw/master/README.txt
Documentation missing; broken external links
The links to the documentation on the project page are broken.
Required Nginx Modules
Upload Progress Module
http://github.com/masterzen/nginx-upload-progress-module
Read documentation
http://github.com/smoothify/filefield_nginx_progress/raw/master/README.txt
improve AHA usage for stream settings: grouping seconds
Hi,
only a little problem, but confuses quite much.
I tried to change the grouping seconds for a heartbeat stream. I opened the stream configuration, activated the textfield for grouing seconds via mouse click, changed the number via keybord, klicked to save button and: got an error and field value was set to 0!
I took 20 min until I recognized by chance, that I have to leave the text input field before pressing the submit button...
Is there any solution for submitting without leaving the input field before?
improve AHA usage for stream settings: grouping seconds
Hi,
only a little problem, but confuses quite much.
I tried to change the grouping seconds for a heartbeat stream. I opened the stream configuration, activated the textfield for grouing seconds via mouse click, changed the number via keybord, klicked to save button and: got an error and field value was set to 0!
I took 20 min until I recognized by chance, that I have to leave the text input field before pressing the submit button...
Is there any solution for submitting without leaving the input field before?
Unable to open sites/default/files/ctools/style/_temporary/* with 777 permission
Hello,
I keep receiving the following errors and I can't seem to fix them:
imagepng() [<a href='function.imagepng'>function.imagepng</a>]: Unable to open 'sites/default/files/ctools/style/_temporary/ec248517a264cf2cfa1971f82727e549/rounded-shadow-background.png' for writing: Permission denied in /home/***/public_html/sites/all/modules/ctools/includes/stylizer.inc on line 584.
imagepng() [<a href='function.imagepng'>function.imagepng</a>]: Unable to open 'sites/default/files/ctools/style/_temporary/8a13c3f759e1af8512ace925fae6ed0f/rounded-shadow-background.png' for writing: Permission denied in /home/***/public_html/sites/all/modules/ctools/includes/stylizer.inc on line 584.
Both of the file folders are set to 777 permission. Does anyone have any idea what may be causing this?
Thank you
Unable to open sites/default/files/ctools/style/_temporary/* with 777 permission
Hello,
I keep receiving the following errors and I can't seem to fix them:
imagepng() [<a href='function.imagepng'>function.imagepng</a>]: Unable to open 'sites/default/files/ctools/style/_temporary/ec248517a264cf2cfa1971f82727e549/rounded-shadow-background.png' for writing: Permission denied in /home/***/public_html/sites/all/modules/ctools/includes/stylizer.inc on line 584.
imagepng() [<a href='function.imagepng'>function.imagepng</a>]: Unable to open 'sites/default/files/ctools/style/_temporary/8a13c3f759e1af8512ace925fae6ed0f/rounded-shadow-background.png' for writing: Permission denied in /home/***/public_html/sites/all/modules/ctools/includes/stylizer.inc on line 584.
Both of the file folders are set to 777 permission. Does anyone have any idea what may be causing this?
Thank you
All classes called "a region"
It seems that the old version of the module (alpha-1) worked well in showing all the regions. But in alpha-2 and dev, I just get Body>a region>a region...>a for example.
Is it just my own install or a general bug?
All classes called "a region"
It seems that the old version of the module (alpha-1) worked well in showing all the regions. But in alpha-2 and dev, I just get Body>a region>a region...>a for example.
Is it just my own install or a general bug?
Importing sites with shared and/or prefixed tables
First, and most importantly:
(11:44:55 AM) vertice: [...] we dont really support shared tables =P
But if you're stuck needing to import existing sites that are using shared/prefixed tables, some of the advice below may help:
(12:09:53 AM) ergonlogic: has anyone here ever imported a site with shared user tables?
(12:10:11 AM) ergonlogic: any gotchas I should be aware of?
(12:13:25 AM) omega8cc: ergonlogic: it is possible to import and run (migrate etc) sites with shared originally tables but you have to clone the same database for every site and effectively split them, since Aegir requires each site to have its own db
(12:14:25 AM) ergonlogic: omega8cc: thanks, that's what I was thinking
(12:14:44 AM) omega8cc: ergonlogic: so to have prefixes working you would need to use custom included php file for every settings.php
(12:15:04 AM) omega8cc: to avoid doing that in global.inc
(12:15:19 AM) omega8cc: it is a new feature btw
(12:17:07 AM) ergonlogic: omega8cc: I saw some stuff about that with Domain Access, I believe
...
(12:20:43 AM) omega8cc: ergonlogic: yes, and now you can do that for DA not only on the global.inc level
...
(12:21:35 AM) ergonlogic: is that documented anywhere outside the code, by any chance?
...
(12:23:31 AM) omega8cc: ergonlogic: it is in the commits comments for sure, and in the settings.php
Importing sites with shared and/or prefixed tables
First, and most importantly:
(11:44:55 AM) vertice: [...] we dont really support shared tables =P
But if you're stuck needing to import existing sites that are using shared/prefixed tables, some of the advice below may help:
(12:09:53 AM) ergonlogic: has anyone here ever imported a site with shared user tables?
(12:10:11 AM) ergonlogic: any gotchas I should be aware of?
(12:13:25 AM) omega8cc: ergonlogic: it is possible to import and run (migrate etc) sites with shared originally tables but you have to clone the same database for every site and effectively split them, since Aegir requires each site to have its own db
(12:14:25 AM) ergonlogic: omega8cc: thanks, that's what I was thinking
(12:14:44 AM) omega8cc: ergonlogic: so to have prefixes working you would need to use custom included php file for every settings.php
(12:15:04 AM) omega8cc: to avoid doing that in global.inc
(12:15:19 AM) omega8cc: it is a new feature btw
(12:17:07 AM) ergonlogic: omega8cc: I saw some stuff about that with Domain Access, I believe
...
(12:20:43 AM) omega8cc: ergonlogic: yes, and now you can do that for DA not only on the global.inc level
...
(12:21:35 AM) ergonlogic: is that documented anywhere outside the code, by any chance?
...
(12:23:31 AM) omega8cc: ergonlogic: it is in the commits comments for sure, and in the settings.php
Forum should be in core
Forum should be in core
Drupal is not just for geeks. Many users want this out of the box. There is NO alternative forum so far in the downloadable drupal tar/zip either as core or contrib module.
- Drupal is thousand times more more useful and attractive if its core contains forum out of the box
- Drupal with forum has made it popular - do not back stab for the sake of any reason
- There are really more important issues than this to clog future dev/works with
- What happens to those massive number of sites who upgrades to D8 from D6/D7 with fourms
- If forum is dropped why not the blog? It is poorly developed compared to wordpress, for example
- If forum is dropped why not the book or wiki? It is poorly developed compared to mediawiki
- If forum is dropped why not search? Drupal already recommends use of Solr search
(crossposted the points)
Forum should be in core
Forum should be in core
Drupal is not just for geeks. Many users want this out of the box. There is NO alternative forum so far in the downloadable drupal tar/zip either as core or contrib module.
- Drupal is thousand times more more useful and attractive if its core contains forum out of the box
- Drupal with forum has made it popular - do not back stab for the sake of any reason
- There are really more important issues than this to clog future dev/works with
- What happens to those massive number of sites who upgrades to D8 from D6/D7 with fourms
- If forum is dropped why not the blog? It is poorly developed compared to wordpress, for example
- If forum is dropped why not the book or wiki? It is poorly developed compared to mediawiki
- If forum is dropped why not search? Drupal already recommends use of Solr search
(crossposted the points)
how do you limit what is shown on form used to edit properties of CCK field
Hi
I have a CCK field with a drop down list of values.
From time to time these values will need to change.
I will like to offer users who belong to a certain role access so that they can add/edit/remove values from the drop down list.
But I do not want to give these users access to other properties related to the field.
So is there a way based on user roles to only show the "Allowed values list" part of the form used to manage cck fields.
Thanks
how do you limit what is shown on form used to edit properties of CCK field
Hi
I have a CCK field with a drop down list of values.
From time to time these values will need to change.
I will like to offer users who belong to a certain role access so that they can add/edit/remove values from the drop down list.
But I do not want to give these users access to other properties related to the field.
So is there a way based on user roles to only show the "Allowed values list" part of the form used to manage cck fields.
Thanks
Feature Request: Restrict user to be able to view only future content, not past
I have been using the Premium module on 2 other sites for awhile now. It does exactly what those sites need.
I am now taking on a new project that is taking a little different twist on the subscription model. They would like to allow users to only view future created content and not have access to content that was previously posted. They are going to offer those previously posted articles as individual products for sale.
In short, I need the ability to restrict access to specific content types based on the post date and the user's creation date. This may be outside the scope of this module. If so, does anyone have any suggestions for how to accomplish this?
Thanks!
Feature Request: Restrict user to be able to view only future content, not past
I have been using the Premium module on 2 other sites for awhile now. It does exactly what those sites need.
I am now taking on a new project that is taking a little different twist on the subscription model. They would like to allow users to only view future created content and not have access to content that was previously posted. They are going to offer those previously posted articles as individual products for sale.
In short, I need the ability to restrict access to specific content types based on the post date and the user's creation date. This may be outside the scope of this module. If so, does anyone have any suggestions for how to accomplish this?
Thanks!
Database not synching
So i installed a new Drupal 6 installation and then a new smf installation, and the smf is in the folder of the drupal installation. I can login with the admin account into drupal, click on the forum link, and it logs into the forums no problem. Unfortunately the users i created before installing the smf are not synching to the smf. It does not log them in and if you try it manually it says user does not exist. If you login to smf via the admin, and look at the users list, it is empty. Please help!
Database not synching
So i installed a new Drupal 6 installation and then a new smf installation, and the smf is in the folder of the drupal installation. I can login with the admin account into drupal, click on the forum link, and it logs into the forums no problem. Unfortunately the users i created before installing the smf are not synching to the smf. It does not log them in and if you try it manually it says user does not exist. If you login to smf via the admin, and look at the users list, it is empty. Please help!










