Example:
My settings:
=======
Conten type: article
Node Block : Enabled
scenario:
======
I have created 1000 articles . node block module is creating blocks for all the 1000 articles . Need to restrict node block module to create blocks whenever needed.
Propose:
=====
Even though nodeblock settings is enabled true, while creating article need to have restriction whether the Block has to be created or not.
Default node block settings should be YES.(Create the node block:YES) while creation of content type article.
Issue i have faced:
===========
I have created around 1000 Articles using Devel module. When I go to /admin/structure/block i could see the following error
"Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 49 bytes) in /var/www/fyn_1.0/includes/common.inc on line 6343"
I have also increased the memory limit to 512MB to render the block list which takes more than 61806.79 ms to load.So i have disabled the Module and updated in your ticket #2613
The page execution report is
"Page execution time was 61806.79 ms. Memory used at: devel_boot()=5.09 MB, devel_shutdown()=247.57 MB, PHP peak=404.25 MB."
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | nodeblock-limit.png | 7.73 KB | kingfisher64 |
| #2 | weight-analogy.png | 9.54 KB | kingfisher64 |
Comments
Comment #1
niklp commentedAm I right in saying that you're *purposely* creating a thousand blocks with one article in each?
There is no realistic scenario where this is necessary, and in any case it is not a sensible move. You should perhaps explain why you think you need to do this, and perhaps someone can explain a better way of doing it! :)
Comment #2
kingfisher64 commentedI believe I know what AravindM is saying, as I came to this thead wondering how to restrict the amount of nodes that get displayed as a block.
He is stating that he has 1000 articles on the site. He wishes some of those articles to be displayed as a block. However because there is only a filter which when makes blocks for ALL nodes of a specific content type he is lumbered with every article becoming a block, (which is blocking up the blocks page) - regardless of whether he wants to use it or not.
The request is for there to be an additional filter on the nodeblock backend (once enabled is clicked) to specify individual node #ID's or a number limit to the amout of nodes that can be made into blocks from a content type to make into a block. I 100% agree with this. :)
Scenario - I have 40 articles, 15 of which i want to display in a block region the other 25 just get displayed as articles in the content zone. How at present would I restrict ALL articles in the blocks backend page from being created as a nodeblock?
Maybe something similar to what the weight module has? (screenshot attached).
Comment #3
kingfisher64 commentedSomething like this (screenshot attached)
Comment #4
kingfisher64 commentedHas anything been decided on this?
I want to enable this module for article content type but can't because that would create so many excess/un-needed blocks in the blocks page. Is there going to be a way to select the node to turn into a block by ID or limit the number of blocks that have this feature.
A reply would be appreciated.
Comment #5
michaellander commentedAravindM & kingfisher64, at this time I'm not going to add any new features to that extent on the current branch. Right now I'm contemplating going in a new direction while maintaining the general premise of this module. Whether it be the rules module, or some other setup. This would likely be under a different module name. If I don't go this route, I may at very least create a 2.x branch to rework the architecture a bit and add some new features.
Have you considered maybe using a views block or something instead?
Also, I'd be very interested in hearing any ideas you may have for future versions.
Comment #6
kingfisher64 commented