Editable Home Page Centerboxes [Support]

gjh42:

The superfluous files may be proper parts of a standard define page, but as the middleboxes are not being used that way, only the files required to allow the Define Pages Editor to handle them are needed here. I'll experiment to see for sure which ones are necessary.Cool.. I did what I thought was the right way..:laugh: But I know there's always more than one way to skin a cat so to speak.. I leave it in your more than capable hands as to the correct manner of execution..

gjh42:

For v1.5.0 compatibility, I am reading mixed signals from those who fully understand admin configurations... "Pages" are supposed to be registered, but there are also comments about using the same (corrected) SQL, presumably for current mod writers to apply. I don't know if this configuration group represents a new page that needs additional handling.
Any file upgrades will be straightforward.

My current code is all contained in one holding file, and still needs to be distributed into individual new and modified files for use.I saw that.. Also on that similar vein there are the questions on how custom product types and whether or not they should be "registered". niccol has an open question on the 1.3-1.5 topic area on how custom product types will work in the new v1.5 world. I am awaiting answers on this as I have a custom module that uses custom product types too..

gjh42:

I think lots of mod writers copied the wrong example - swguy gives a long list of mods that all have the same issue.Yep, and all the ones I've had my little hands in will be updated to remove the error.. I've already updated Ty Package Tracker to remove this "bug".

gjh42:

The "sideboxes in the center" idea would be great, but I had been thinking that it would require completely different handling. A thought just occurred to me that perhaps the define page file could be written to require/include the desired sidebox module file, which would then use the sidebox tpl_ file... It would probably be necessary to include a bunch of setting statements in the define so that the sidebox believed itself to be in the right environment, and might not be possible without widespread code changes (not practical)... we'll see:)I wonder if the Sideboxes Anywhere code might provide some insight on how to support this..:smile: You would know better than I if this code is adaptable..

Yes, Sidebox Anywhere may well show how to handle it. The main question is if the manual setting of variables needed to allow a sidebox to operate in the center will interfere with other sideboxes, perhaps in the right column. At any rate, I wouldn't be getting into that at this point. If this control upgrade succeeds, that will be enough for one release of the mod.

gjh42:

Yes, Sidebox Anywhere may well show how to handle it. The main question is if the manual setting of variables needed to allow a sidebox to operate in the center will interfere with other sideboxes, perhaps in the right column. At any rate, I wouldn't be getting into that at this point. If this control upgrade succeeds, that will be enough for one release of the mod.Ahhhh and once again, you have taken my idea and turned it into a PROPER add-on.. :laugh: Next time I'm just gonna come straight to you!!!:smile: Looking forward to see if in a future edition if you can work out how to display sideboxes in the center area too.. :)

I have the files modified and updated, with a couple of improvements over the posted code, except for the SQL. That is updated for function and avoiding the config_group 0 bug, but I have still not been able to find out how to make it unequivocally work in v1.5.0.
I can't spend more time on it now, as I have to finish the graphics for a festival ad to go to the printers tomorrow (no pressure:)
I'll see if I can attach a zip (it may be too big).

Okay, found the thread with accurate and complete information (post 13) on SQL for setting up and registering new configuration groups. Still not sure how it would all be done programmatically (where are there examples of the whole shebang?), but an install.sql will work.

I have (I believe) updated the SQL correctly to v1.5.0 compatibility, and tried an install on a fresh v1.5.0 on my local server. The SQL patch went smoothly, and all of the entries show up in the database as they should, in admin_pages, configuration and configuration_groups tables. The db fields look consistent with other adjacent fields. However, the Editable Centerboxes item never shows up in the Configuration dropdown or in the altnav, even after logging out and back in. Guess I'll scan the thread for info on this, unless someone can offer suggestions quicker than that:)

The define pages show in Define Pages Editor as they should. The existence of the base define_middlebox_x.php file is necessary to the display of the /your_template/define_middlebox_x.php, but none of the other define page files are needed with the exception of one /includes/extra_datafiles/middlebox_filenames.php with all nine pages' info.

Navigating directly to /myadmin/configuration.php?gID=31 brought up the Editable Centerboxes page, and I was able to change any desired settings. After a few minor bugfixes in files, the centerboxes are working correctly in whatever location I assign them to.

So the only remaining problem is why the configuration group is not showing in the Configuration menu.

Got the answer here, and everything appears to be working correctly.

The zip is far too big to attach, so please PM me if you would like a copy to test.

does this work as well as showing category images on the home page now???

gazag:

does this work as well as showing category images on the home page now???
This add-on has always worked and never STOPPED category images from showing on the main page.. Glenn's changes are improvements to how the centerboxes are managed (better coding), and to make it v1.5 ready.. but the basic functionality of this mod is the SAME..

DivaVocals:

This add-on has always worked and never STOPPED category images from showing on the main page.. Glenn's changes are improvements to how the centerboxes are managed (better coding), and to make it v1.5 ready.. but the basic functionality of this mod is the SAME..

Ok what have i done wrong then? When i go to ADMIN > CONFIGURATION > LAYOUT SETTINGS and enable 'Categories - Always Show on Main Page'

All my centerboxes disappear!!!!!:wacko:

gazag:

Ok what have i done wrong then? When i go to ADMIN > CONFIGURATION > LAYOUT SETTINGS and enable 'Categories - Always Show on Main Page'

All my centerboxes disappear!!!!!:wacko:Go back to the readme document and/or the admin settings for this add-on.. you have to have VERY SPECIFIC settings for this module depending on whether or not you have categories enabled on your main page.. My guess is you don't have the right settings for this module..

Tested out an install of the version 2.0beta (1.5 ready) on my test site and it went flawlessly. A great mod now even better. Also read through readme a few times and (genuinely) couldn't find anything much wrong there either! Just one missing "to" from the sentence "Initially I wanted to be able place specific..." on Description page.

I can't see that the changes in ver2 need anything done on the 'troubleshooting' page.

It may be worth adding some extra info about the box titles being set in the extra_definitions/middlebox_defines.php file? (I think that's right)

Confession time - I'd never tried the uneven column aligning 'hack' described in 'additional ingormation' (with screenshot). Simply didn't work for me however much I fiddled with the CSS. It 'sort of' worked in an old IE version (but looked ugly - crept over the footer), but not at all in any recent Firefox - just went 32k pixels down the screen! Has this become redundant? Shame if it has, but anyone aware of any other way as would be nice if it worked?

pinkduck:

Simply didn't work for me however much I fiddled with the CSS.I know you think this is descriptive.. It's simply not.. It's difficult to troubleshoot things reported as "broken" without seeing it "broken" to determine the problem.. That said a link to your store with the code you tried in place would help..

OK. Managed to get the 'balanced column height' effect working (as described in Additional Information in the readme). For some reason the necessary outer div id when generated had an extra numeric attached (for example #navColumnMiddleWrapper2) which detached it from the id in the CSS.

Not sure why it's happening or how variable it may be, but either changing the #navColumnMiddleWrapper class in the CSS to suit, or (perhaps better) changing the class to an id (so make it .navColumnMiddleWrapper for CSS line 2) might at least be an interim fix.

Thanks again for letting me test.

pinkduck:

Not sure why it's happening or how variable it may be, but either changing the #navColumnMiddleWrapper class in the CSS to suit, or (perhaps better) changing the class to an id (so make it .navColumnMiddleWrapper for CSS line 2) might at least be an interim fix.

Thanks again for letting me test.You're mixing up classes and IDs. #navColumnMiddleWrapper is an ID, not a class.. Simply changing it to a class is not the right approach as there are distinct reasons to use classes versus IDs the discussion of which will be a tad off topic for this thread.. Glenn would know better than I since it is his code driving this version whether this is a necessary, but if the code cannot be modified so that the number is not appended to the #navColumnMiddleWrapper ID then a simple update in the readme instructions explaining what CSS modifications are required should suffice..

Since there can be more than one #navColumnMiddleWrapper on a page, each one must have a number appended to make its id unique. Each wrapper also has a class tag, .navColumnMiddleWrapper, so you can use that in the stylesheet to address all middlebox groups.
The readme and/or the stylesheet should be modified to address this fact.

gjh42:

Since there can be more than one #navColumnMiddleWrapper on a page, each one must have a number appended to make its id unique. Each wrapper also has a class tag, .navColumnMiddleWrapper, so you can use that in the stylesheet to address all middlebox groups.
**The readme and/or the stylesheet should be modified to address this fact.**I figured as much.. I haven't tested yet (plan to do so this week), but I love how you took my little seemingly convoluted idea to the next level.. I could have never make it function as you now have it functioning!! Well done..
:clap:

hi all, i installed the addon/SQL but it is not showing anywhere, neither in configuration->layout setting nor in configuration. I'm running on 1.5...Could anyone ghelp me with this? thanks a lot!

The version currently in Free Addons will not work correctly in v1.5.0. I have updated it and offered the new version for testing (it's too big to attach to a post). I am going to be out of touch for the next week or so; maybe Diva can send you a copy of the zip?