[support] blocks do not display
Roger
arelem at bigpond.com
Mon Sep 10 03:52:13 UTC 2012
On 09/10/2012 01:32 PM, Roger wrote:
> On 09/10/2012 10:13 AM, support-request at drupal.org wrote:
>> <1347211403.55137.YahooMailNeo at web181606.mail.ne1.yahoo.com>
>> Content-Type: text/plain; charset="iso-8859-1"
>>
>> My advice, which most will, I am sure, agree with is to not mess with
>> a core install. Don't second guess which tables are needed. Most
>> tables are created only when a feature/module is enabled. Therefore,
>> they are all needed. If you don't want certain tables, don't install
>> the module that creates them.
>>
>> The cache tables are required even if you have caching disabled.
>> Regardless of that setting, your system is caching. Likewise, the
>> registries (more than one) are required and cannot be missing.
>>
>>
>> Backup and Migrate doesn't create tables, AFAIK, it just makes backup
>> files.
>>
>> Who told you that OG does not play well with Panels? The fact is that
>> OG would prefer to create panels for you.
>>
>> ?
>> Nancy
>>
>> Injustice anywhere is a threat to justice everywhere. -- Dr. Martin
>> L. King, Jr.
> Thank you Nancy.
> I'll try og with panels, on your recommendation, it may solve a problem.
> However nat and workbench are two that I do not want in the new
> sandpit and neither can be removed just by switching off and deleting
> the modules.
> Workbench in particular once initiated, seems very difficult to
> eliminate.
>
> I'm not messing with or second guessing core. I understand that most
> tables are created when a module is installed.
I just now, included system, registry, registry_file, now it all
displays as intended with one exception that I rather like. All blocks
now display but are disabled so I can manage blocks as needed.
Excellent, thanks Nancy you helped solve this dilemma.
More information about the support
mailing list