Just applied the new security patch - it (or I) have problems -

When uploading new image in gallery:

Warning: include(templates/g/skin_global.php) [function.include]: failed to open stream: No such file or directory in /iwiccle_101/index.php on line 122

When uploading image in articles or blogs or groups:

Fatal error: Cannot use string offset as an array in /iwiccle_101/core/class_uploader.php on line 106

Reloaded the old index.php file - problems eliminated.

More on this as I continue fiddling.

Odd --- that part of code was not modified at all. Did you make any other changes? Do you have iWiccle 1.00 or 1.01 installed?

What's the reference to templates/g/skin_global.php? Do you have a custom skin defined? If so, does the file above exist?

Looks like there's a variable name wrong on line 106 of class_uploader. Change the line

• $data['upload_parent_id'] = $_SESSION['module'][$_SESSION['module']['module_ident']]['my']['parent_id'];

To:

• $data['upload_parent_id'] = $_SESSION['member'][$_SESSION['module']['module_ident']]['my_parent']['parent_id'];

That's a quick fix for you. Do confirm your version first. The uploader class references a deprecated variable, and for some reason your PHP interprets it as a string offset -- not as undefined index, as I'd expect it to.

For the life of me I can't see how the changes I made for the patched files could cause this... Let's see. Does the above fix it? (And please confirm your version.)

Ok, here goes:

Running version 1.01

Changed the line in class_uploader - not getting the fatal error any more.

Still getting the templates/g/skin_global.php error.

I have not changed the skin_global file - I have changed the menu names via the menu builder.

skin_global.php exists in the templates/default directory.

I have no such thing as a templates/g directory.

If I revert back to the old (pre-fix) index.php file all errors dissapear.

Hope the above makes sense. Thanks,  John

For some odd reason, you seem to have "g" selected as the current skin! Please go to Site > Skins and reset "default" as the default skin.

If you want to revert the bit of code causing this (but only if the above fails and we can't find anything else to fix it with), the difference causing this (index.php) is as follows:

if ($core['init']['default_skin'] != "default")
{
    include(PATH_TEMPLATES."{$core['init']['default_skin']}/skin_global.php");
}
else
{ // make skin

    require_once(PATH_TEMPLATES."default/skin_global.php");
}

The old version has it:

require_once(PATH_TEMPLATES."default/skin_global.php");

if ($core['init']['default_skin'] != "default")
{
    include(PATH_TEMPLATES."{$core['init']['default_skin']}/skin_global.php");
}

And if you want, you can change this as a temporary fix assuming you aren't using custom skins right now.

Checked skin - it was showing 'default' (no other option) - reselected default and saved it.

Problem still persisted.

Changed index.php as per instruction - got the following when trying to upload image:

Warning: include(templates/g/skin_global.php) [function.include]: failed to open stream: No such file or directory in /iwiccle_101/index.php on line 124

Have reverted back to the old index.php. - all seems to work well.

Could you please zip and e-mail me the two index.php files you have? I want to be sure we're looking at the same thing!

Markus, zipped files have been emailed to your wiccle address.

Warning: include(templates/e/skin_global.php) [function.include]: failed to open stream: No such file or directory in /home/youreme/public_html/youtofun.com/index.php on line 122

Warning: include() [function.include]: Failed opening 'templates/e/skin_global.php' for inclusion (include_path='.:/usr/lib/php:/usr/local/lib/php') in /home/youreme/public_html/youtofun.com/index.php on line 122

What exactly do you do when this happens? If when trying to upload an image, at what point in the process? Screenshots, anybody?

I myself Technoman have guided and helped install Wiccle with videophotogr the new guy who registered here today and there is an error in index it says and hes using the linux cpanel ...

it has been hours we have tried to figure this issue out and we just cant seem to find out why its occuring

Thanks for helping Steve, are you able to take a screenshot or quick video for Markus ? If Markus can re-create the problem or see it, then we can fix it. It is a strange bug that we just cant seem to re-create here, so any help will help us make sure this bug never appears again! :)

If anyone can give me temporary FTP access to a server where this problem occurs, I can test and fix it in fifteen minutes for everyone. Right now I am unable to track the problem source, because I am unable to replicate the problem at my end.

This problem has been addressed here.

• iWiccle requires that the register_globals PHP directive be turned off. The incorrect setting will be detected & auto-fixed runtime in iWiccle 1.10, but you should turn it off in any case.

ok videophotogr  and I have met threw yourtube a week ago,

I have been trying to tell him that dolphin is very buggy and then persuaded him to  come over here and try wiccle and told him that it will be the ultimate choice he would make, since wiccle is user friendly in its own way and much easier to navagate for say the average user then dolphin

originally I was going to guide videophotogr  in installing Dolphin but thats when i told him that i been with dolphin for almost 4 years and nothing has gotten any better, if anything dolphin is way to big and no matter what server you got its slow and to buggy and the waitting time is a never ending thing plus the whole complete admin section is way complicated to the average user, for the mean time Yes I presented videophotogr  to come here and try wiccle software out and so he had said no problems as long as was going to help him threw it.

After realizing videophotogr  was working on a LINUX CPANEL i had to learn myself going threw with steve on how to get this wiccle installed and pufffff the errors we started to get 3 days ago ...

remember guys I work ONLY with Windows so learning Linux and CPANEL which seems a bit easy after watching some youtube videos and voila we were able to get a database and domain tranfered properly to his control panel and then  once we isntalled it 3 days ago since then me and videophotogr  havent really spoke cause we both got lives outside of this and I am hoping today or later tonight him and I can fix this error and then play around with it on his server ...

If markus you want information to his server i will need to ask him and then he will email you or private message you for assistance if you dont mind ...

thanks and if I do come across others down my journey who want a social community site I will defently address them here to wiccle site!

Thanks Technoman, much appreciated! Every software will have its bugs, the questions is one of attitude towards them. I feel personally uncomfortable as long as the code I write doesn't work exactly as it ought to, and we will do everything within our power to get every reported bug fixed within a reasonable timeframe --- I don't expect to see a situation where bugs would hang around for weeks without a fix. If bugs are so damned hard to fix, there's something wrong with the program architecture itself.

Any problems you may face when doing the installation, feel free to bring it up in the forums and we'll fix it up. N.B. Even if I may do troubleshooting in private or over e-mail, let's try to keep 99% of all support and troubleshooting in the forums to make sure everyone benefits from our situations and solutions.

I just contacted my server comapny JaguarPC to see if the could turn off the Global PHP just for one site (I have 3) on my server for the Wiccle YouToFun.com account.  Here is their reply:

please advise what you exactly mean by global php? If your application does not need php then you can are not supposed to stop php or disable it for any account.

Or do you want to set special setting for your single account that you don't want to be prominent for other account? If yes, then you can place the local copy of php.ini file in that particular account and edit is as you wish.

"The register_globals PHP directive should be turned off." Just say that. It's important to repeat setting names and the such verbatim, unless you are sure your rewording makes sense.