Hi which version can I use on 1.3.8a
Many Thanks
Regards
RR
Hi which version can I use on 1.3.8a
Many Thanks
Regards
RR
Don't use it on v1.3.8a; upgrade to v1.3.9h and use the latest mod version, if you can't upgrade to v1.5.0 now.
I have been working on the details of integrating the control improvements into the mod, and have a number of suggestions.
First, a change in the install sql, per swguy's post, to avoid a common mod bug that deletes configuration_group 0 on initial install.
Trimming completely unnecessary files from the package. Several of the files (repeated 9 times) are never used for anything. Some of the files can probably be consolidated into one middlebox_filenames.php and one middlebox_defines.php file.
I will test these changes on my development site when I have time, and will be happy to send you a full set of the proposals if you want to work on them now.
It may work on v1.3.8a; I haven't tested it. V1.0 of the mod will definitely work. It is more basic, but should still do the job you want.
My Site - Zen Cart & WordPress integration specialist
I don't answer support questions via PM. Post add-on support questions in the support thread. The question & the answer will benefit others with similar issues.
I'm glad you are working on this, as the changes you are making to improve this are necessary but a tad over my head to implement.
The SQL bug in this mod is truly as a result of "monkey see, monkey do". I copied off of someone else's homework (Fual Slimbox I believe), not knowing at the time that I was copying an error... Won't be making that mistake again.
Some of the files you see in the current version are there because frankly I did not know another way to do this other than what you see executed..I assumed that for each editable box, you would need a separate editable defined page.
It was a down and dirty solution for a site I was working on at the time, and I shared it because I thought others might want this kind of functionality as well.. I was trying to replicate a feature available in WordPress where you can create themes with "widgetized areas" located in places other than the sidebar.
I wanted to be able to show/display admin editable content along with specific sideboxes in the center content area of the homepage. I stuck with using defined pages for the centerboxes because I did not know how to get specific sideboxes to appear in the middle content area of the home page and so I used the defined pages instead to "recreate" the sideboxes I wanted to display in the center..
It would be nice if these centerboxes could display specific sideboxes as well as allow for admin editable content. (hint hint..)
I would be very interested in testing the code to if you don't mind sending me a copy.. I'll PM you my e-mail info.
My Site - Zen Cart & WordPress integration specialist
I don't answer support questions via PM. Post add-on support questions in the support thread. The question & the answer will benefit others with similar issues.
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.
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 think lots of mod writers copied the wrong example - swguy gives a long list of mods that all have the same issue.
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:)