PHP Errors: [2010/01/30-02:07:19]

Notice: Undefined variable: lay_dropdown in C:wampwwwdomain.comcoreadminadmin_area_modules.php on line 147



Warning: Invalid argument supplied for foreach() in C:wampwwwdomain.comcoreclass_global.php on line 856

Confirmed cosmetic bug in Admin CP > Modules > [module without layouts]

This is because the lay_dropdown fetches all builder layouts created under any given module when you edit a module, and since the Admin module doesn't use layouts or the builder, there are none listed -> notice on the dropdown not generated.

This is a harmless cosmetic error that will not affect the way your software works, even if you click "Save" on this particular page. In general, there isn't much in the Admin module editing area that would do anything for you at all. The only thing you can change here is the rollover description that is shown, in the event that you choose to show "Admin" as one of the tabs in your main menu.

If you want, this is easy enough to fix right away. /core/admin/admin_area_modules.php #142, add the following line:

        $lay_dropdown = array();
        while ($lay_data = mysql_fetch_assoc($resource[0]))
            $lay_dropdown[$lay_data['lay_ident']] = $lay_data['lay_ident'];

Otherwise, the fix will be included in the next release. As it's only cosmetic, I'm not releasing a separate patch file for it.

ok so next release this will be fixxed?

when is the next release if you dont mind telling me?

Thank you for responding, but im not about to play with codes ...  :) ... i don't like playing with codes but I know that this method that your showing above is what i could do to change it is by adding some code that you suggested ...  but I guess I will just wait until next release no biggy ;)

Every bug you see me posting a fix to is already fixed in the main code trunk, and as such will naturally be rolled out with the next release.

We are already releasing patch files prior to the next release for bugs that limit expected functionality. Whenever they mount up to something that's worth releasing as a maintenance upgrade, you'll have a next minor release. The next major release will happen sometime following the release of Wiccle Web Builder. We are still in the aftermath of the iWiccle 1.20 landmark release, and are preparing for the final stretch with our flagship website creation suite.

But as I said, this issue is only cosmetic and in no way affects your site operation or limits the options you could configure.

I had to unistall it cause I was getting php define errors on homepage to, so what im going to do is reinstall it overnight and then start over and repair erorr for error until I can reasure that its running 99%

I will get back to you on how it goes by tomorrow afternoon/evening

Good luck, and don't forget to log the errors and URLs of error pages while you're at it, if you come across any further errors anywhere. You can also take a dump of the w_error_log table of your database and post that in to help in debugging. See also: iWiccle Error Logging

line 142 has already something as shown here

142  while ($lay_data = mysql_fetch_assoc($resource[0]))
143. $lay_dropdown[$lay_data['lay_ident']] = $lay_data['lay_ident'];
144
145
146 if (empty($data['module_default_page'])) $data['module_default_page'] = "home";
147 $data['lay_dropdown'] = Utility::generic_dropdown($lay_dropdown, $data['module_default_page']);

replace this code ?

142 $lay_dropdown = array();
143 while ($lay_data = mysql_fetch_assoc($resource[0]))
144 $lay_dropdown[$lay_data['lay_ident']] = $lay_data['lay_ident'];

let me know how to do this since there is already a code in place of 142 143 etc...

thanks

Before the:

while ($lay_data = mysql_fetch_assoc($resource[0]))

Add this:

        $lay_dropdown = array();

Or in other words, what's blue in the earlier snippet is what you should insert before the gray code.

I will wrap up a minor maintenance release and an all-in-one patch file for release 1.20.2 tomorrow. It will not feature any database changes, or any changes to templating, so it's just a quick file upload operation. If getting this cosmetic bug in order is not critical right now, you might as well wait for tomorrow and get it done with more easily.

These issues have been fixed in the 1.21 update.