The problem seems to be happening only after i uploaded the new .... i think its called ...

whatever the php file is called that fixes LEGACY issues after the upgrade to 1.20 iWiccle.

I have a couple photos in the gallery from BEFORE the upgrade
but anything i have been trying to upload (images anywhere actually ) to the gallery and other modules, well

they upload and i see them initially in the POST screen,

but once i get to the public side ( finished page ) its not there

nor is it there when i goto EDIT the post or gallery upload.

ok i was able to go into more testing so this is what happened

I was able to get to my php.ini file and changed it to read

allow_url_fopen = On

which i found was the problem causing me to NOT have the ability to UPLOAD FROM URL

well i can now upload image from a URL into different modules

but

now i cant simply upload from my machine, any image

EXAMPLE:
when i upload a new image into the gallery
the file path is correct
the file NAME its looking for is incomplete.

Its supposed to be looking for

s60_gallery-1-1264653150_3d-robot-girl.jpg

but instead when i load the page after upload
and i see the image is..well trying to be called but nothing is showing,
i copied the IMAGE URL and pasted it, which shows its looking for

s60_

ok.....new to me

Yes that'd be the correct setting to switch -- good thing your host allows you to change that. Some shared hosts switch it off and don't allow changing. (And it's a bit of guesswork there on what all some host may or may not disable.) I need to include this in a FAQ and include an optional check into the installer as well to inform the user of this.

Could you regive me posting level permissions at your site so I can test this again? (I do see working images in your Gallery.) If you're doing a clean install, or don't have previous gallery images, please neglect the gallery_config.php legacy file -- it's only there to carry your old images over, and shouldn't be used otherwise. (By the looks of it this is already the case on your site, but here's for the record for everyone else.)

ok Markus

i changed your permissions level just now

log in and give it a shot

the images you currently see in thegallery are images added VIA URL,

not uploads.

When adding image via UPLOAD, i do see it in the corect module folder in FTP but it just isnt showing on the public end.

Another question (PHP.INI related)

What other things should be ON or TRUE or ACTIVE in php.ini for it all to work

Because my host leaves a php.ini.sample file which i can add in or comment out certain functions.

There is a confirmed bug in the Gallery inline uploader. Here's the fix.

There is a little conflict in the new upload-from-URL and inline uploader combo. In some situations, the URL data negates the valid uploaded image. This issue has now been fixed. If you want to change this yourself, open /core/class_elements.php at line #437, and change the following:

elseif (!empty($data['image_from_url']) && !defined("AJAX"))

To this:

elseif (!empty($data['image_from_url']) && strlen($data['image_from_url']) > 20 && !defined("AJAX"))

You can also upload this patch file to correct the issue in your iWiccle 1.20 installation. I wonder how this issue didn't surface earlier. In any case, things should be back in working order for you with this fix.

I will also repeat for reference here (thanks AntiFMRadio for the note) that if you have problems using the "Upload from URL" feature, your host may have disabled PHP from accessing files from remote URLs. To fix that, edit your php.ini to read as follows:

allow_url_fopen = On

CURL image fetching support as an option will be introduced in an upcoming release to ensure this feature will work across different shared hosting platforms.

What other things should be ON or TRUE or ACTIVE in php.ini for it all to work

Posting a separate FAQ thread about this.

Markus thank you very much

that elsif line did the trick. Im very happy we got that solved.

Trust me. If theres a bug to be found in this new version
ill help ya find it for sure.

I have a pretty big plan for the use of iWiccle. Glad i found you guys.

tell your partner i said thanks as well.

Please disregard my PM about phpinfo

obviously this was the solution

Hey, thank you for keeping the reports coming, and I'll keep up the fixing at our end.

Due to limited manpower we haven't been able to put every aspect of the system through heavy enough testing to spot everything, but as you have seen in the bugs so far, most of them are are dead easy and brief to fix (almost invariably so when it's a direct software issue and not an environment issue), and get patched not long after I get around to looking what the issue might be.

"Confirm" and "Fix" tend to go hand in hand, since when you get to the point of confirming it's an actual bug, there are only so many places to look at per each area, and once you look there and see what it's all about, it'd feel dumb to not hack it straight and release a patch when you already know the answer. The only bugs that can take a bit more time to look into are those featuring custom hosting environments.