iWiccle 1.21 has now been released and is available from the download area. More detailed notes on what's new will follow tomorrow. This release features several security upgrades, and as such it's highly recommended that you upgrade from earlier versions.

1.20 -> 1.21 upgrade information will follow momentarily. I am preparing more detailed notes for those who have customized their sites, in the event that some of their changes are affected.

Enjoy the new release!

Well done and Thank You Markus - post 7am and you've yet to go home!!

Your users/customers appreciate and Thank You for it! 

Cheers! Home is where the code is! (And here's to hoping nobody at home reads the forums...)

Now where's that pint of beer... Yea I need to be back attending meeting at 2 pm... Guess I'll go dance with the Leprechauns downtown Galway for a couple of hours, no poing crashing now!

Upgrade script is now available with instructions, repeated below, and I have tested it locally and on the old wilp demo. Be sure to read instructions, should be painless enough an upgrade.

Main features to be upgraded is the security center and the whole IE7 deal (all over again). There's also a small update to the way mail works, you can now quote and archive. (Full custom folder support for 2.0.) I had more in mind I thought of adding in, but held back on anything to do with database structure expansion for now as it's a minor upgrade. As a part of the security overhaul I did a good deal of work on rewiring language processing, so there may be a stray unparsed language string somewhere. Keep your eyes open and report any issues you may encounter.

Whenever I get reports that IE7 is finally tamed with 1.21, I'll crunch in the extra color themes as an add-on. And if not, we'll battle again.

----

+--------------------------------------
|  iWiccle v1.20->v1.21 Upgrade Script
+--------------------------------------
|  http://www.www.wiccle.com
|  Email: info@wiccle.com
|  Time: 2010-02-23
+-------------------------------------


Please read this file from the beginning to the end to know what you're about to do.


HOW TO UPGRADE: 1.20 -> 1.21

- Upload all the upgrade files over the current iWiccle 1.20 files on your server. (If you have customized your templates, read this file first!)
- Launch the upgrade script (upgrade_120_121.php) after uploading the updated iWiccle files to the root (/public_html etc.) of your iWiccle 1.20 installation. You don't need to modify any permissions for the operation.


WHAT DOES THE UPGRADE SCRIPT DO?

- Two fixes to member profile database fields
- Updates mail folders and adds "archived" folder and page layout


BEFORE THE UPGRADE

- Take a full backup of your database and files to ensure you can recover in the event of a failed upgrade (unlikely but cover your bases).



CONFIGURATION NOTES

- There is one new variable in /core/variables.php ($core['sys']['allowed_pages_override']). If you have edited the variables there, you don't need to overwrite all.
- In .htaccess, there is one new line for ^page/ etc. for shorthand for pages under the default module when using smart urls.


IF YOU HAVE CUSTOMIZED YOUR TEMPLATES...

The templates have been improved across the board to extend IE7 compatibility. If you have't edited some of the following files, just replace them with the updated versions.

    CSS CHANGES:

If you have customized your site using the iWiccle Templating Kit, changes to the next three files listed will be sufficient to ensure your site styling customizations will remain intact.  The following changes have been done to the iWiccle general purpose styling CSS files (listed in order of appearance):

    * units.css (changes in: .corner_top_center)
                (new: .unit_content - optional)
                (removed: .unit_area entries)
    * wrappers.css (changes in: .footer_wrapper, .bottom_footer, .column_unit, removed clutter from end)
    * menus.css (changes in: .top_button_mid, .module_menu, module_menu a:link)
                (new: .module_menu_wrapper, .button_new_mail)
                (removed: .site_logo)
   
The following changes have been done to the iWiccle dynamic content and system CSS files:

    * ajax.css (recommend full overwrite)
    * categories.css (changes in: .cat_footer, .cat_image_right
                    (removed: h4)
    * comments.css (recommend full overwrite)
    * feeds.css (deleted as unnecessary -> remove also @import "feeds.css" entry from style.css)
    * favorites.css (recommend full overwrite)
    * members.css (changes in: .member_portal_photo_holder, .member_mini_wrapper, .member_mini_img, .profile_tabs, .profile_tab_unit a:link, )
    * parents.css (changes in: .parent_image_right, .parent_list_row_1)
    * posts.css (changes in: .thread_details, .post_wrapper, .post_wrapper h4, .post_caption, .post_description, .post_metadata, .post_text, .post_footer, .post_assoc_image_holder, .post_assoc_image, .post_moderated, .post_nextprev a:hover, .h1_highlight, .post_tiled_wrap, )
                (new: .caption_holder, post_text h3, .post_text h4)
    * system.css (new: from /* Builder CSS */ onward)
    * wiccle.css (deleted as unnecessary -> remove also @import "feeds.css" entry from style.css)
    * wysiwyg.css (recommend full overwrite)

   
    PHP TEMPLATE CHANGES:
   
    * all around: css class "unit_area" has been removed to eliminate IE7 conflicts
    * skin_units.php (changes: excess repetition trimmed off by including the overlap under "general_unit_header" and "general_unit_content", class="unit_area" removed from all entries under /* Custom unit formats */)
                    (new: "drop left" and "drop right" style units)
    * skin_wrapper.php (changes on lines #70-77, #205-225, #330, #381, #404 (removal), #458 (anchor rewrite tag)
    * other files: recommend full overwrite (if you have customizations elsewhere, please ask at Fusion Forums)
   
   
How to compare files if you need to do it yourself? You can do it for example with Notepad++ (download for free at http://notepad-plus.sourceforge.net) by opening both versions into tabs and selecting Plugins > Compare or clicking ALT+D.

Since I've changed the "Pro" skin design if I just upload the new 1.21 I'll lose those changes. So, I've backed up the database as suggested and downloaded the templates directory so I can re-upload them after the upgrade to keep the new look. Won't that negate the some of the changes you made?

Can you let me know what are the files you have changed to create your new style? Please do that and I'll tell you the guaranteed upgrade path for your specific modifications.

can you specify the changes in language?, i've just finished the spanish translation and need to update

um... Just had a thought (watch out!)

Since I made all the changes to the original file PRO, and created a new template, named dark, in admin based on the PRO template, doesn't that mean I have an exact duplicate of "my" pro template and not your "original" pro template? Which would mean that uploading the PRO template from this new release won't affect my new 'dark' template? How's that for confusing?

As for the other changes I've made like in langues etc...

Cerbero; Great news with the translation! Are we talking 1.20 release or 1.11 release?

Footman; Yes, that'd be correct. If you have your dark template separately, you can safely upload the entire pro template folder there without its affecting anything. (Not that it'll do much good to you as it of course won't be in use!)

You should consider integrating the two to roll in all the IE7 fixes I have done to the templates. If you want, feel free to zip up and mail me the files you've changed to create your dark template, and I'll let you know the situation. (Most likely just copypasting one or two things over from one set of files to the other, if even that. Can't say anything too educated without knowing what all changes you may have made. If you went by the specs in the templating kit, this should be a non-issue.)

Thanks very much Markus

ill get testing on it right this weekend

and ill first POST about anything i find

Good luck and happy testings! The upgrade is straightforward enough for your site, just upload the upgrade bundle, run the upgrade script, and you're done.

Hi it's me again... Ok ran the upgrade script andit was all going along perfectly. It was even showing up with my changed color scheme! I'm feeling really good. Went through the steps - Congratulations! Click here to reload your settings etc... then a blank screen

&*^%#^&^

Yea, this would happen if you haven't done the changes in the skin_wrappers.php for 1.21... Want me to log in over FTP and sort it out?

Sure Markus that would be great. Need me to email you the info again?

:: edit::

email sent - thanks again Markus

Here's the process log for anyone who wants to do debugging in the future.

Footman Debug Session Log

Site showed a blank screen. Took backup of the entire site before starting.

In class_iwiccle.php:

    After #80 and the following:
        require_once(PATH_CORE."variables.php");

    Added the following to dump and review all system settings:
        die(print_R($core));

Reuploaded "templates/pro" folder from default installation. (No success.)

In templates/pro/wrapper.php before "return $output;" added to see if the output was properly compiled so far:
        echo $output;

Result: HTML output is properly compiled and displays when printed from here.

Added in a code snippet after "Scheduled check tasks" to register me as root administrator to ensure I get all output and error notifications.

(Noticed that my new Avast Antivirus gave false positives for trojans in two files, namely events.js and the top_button_mid.png graphic. Verified that they are not infected, scanned the site folders locally to ensure all files were clean. Evidently some over-zealous runtime algorithm glitch in progress... Go Avast. Can't be duplicated, so that was evidently an issue with the antivirus software.)

Returned to class_iwiccle.php, added echo $output; after $output = skin_wrapper();. HTML output is carried over to this point correctly; moving the echo command downward to see where it disappears.

Noticed that output goes fubar at this point:
    $output = Errors::finalize_debug($output);

Continued echoing output inside class_errors.php and the function above. Felt like being in a familiar place, a flashback began to slowly creep in. Looked up error logs. (D'oh.)

    [Wed Feb 24 17:02:27 2010] [error] [client 84.203.209.130] PHP Fatal error: 
    Call to undefined function  memory_get_peak_usage() in /usr/local/apache/sites/---snip---/htdocs/core/class_errors.php on line 178

You'll remember you are on PHP old version, and faced this same issue during the 1.11->1.20 upgrade. Here is the explanation of what causes this: http://www.wiccle.com/forums/public_forums/install__modification/post/post_1179

Edited your class_errors.php file (and the next 1.21 build) to make the memory peak usage call conditional:

    $core['runtime']['memory_peak_usage'] = function_exists("memory_get_peak_usage") ? round(memory_get_peak_usage(TRUE) / 1024) : "N/A";

And things work again as expected. Could have started off with the error_log you had there and avoided doing all of the above. Oh well, here are notes on how you can debug the situation in general if your screen ever goes blank, and if error logs don't tell anything meaningful.

Awesome Markus Thank you!

To be totally honest I don't understand most of what you posted so I'm glad I didn't tackle this fix myself. Probably would of made more of a mess.

However I did come away with something, so it's not a total waste - Change servers to one that can run latest version of PHP.

I'm going to do a little window shopping for a host. I've emailed my host a few times over the month so far asking what they can do for me here and what's needed. After the first email I got a quick response saying they'll send my some upgrade ideas the next day. That was Feb 9. I have yet to hear back from them since. Too bad. I've been with them for 4 years and always had good resonse and help from them. Anyway, so off to find another host I go.

No worries, just glad to see it sorted out and you back in business developing the site.

If you need a second pair of eyes to look at a prospective host, feel free to post a note here. I'd give you an fair offer for a slot on our own servers, but since the boxes we lease go under "no adult content" terms, not much I can do to help you out directly.

Thanks Markus - I was assuming your hosting would accept adult content sites, which is cool. But I will pass my findings on to you here and get your thoughts. I have emails out to 5 adult friendly hosts now.

ps. still haven't heard back from my current host. Guess they don't want the business.

As you know prices for adult-allowed hosting are a bit more steep, and as such it'd create a whole lot unnecessary overhead if we were to go for such servers. Maybe if our software starts getting massive swinger attention for some reason, we can revisit that!

Oh yeah... I know all about paying more for adult hosting. They tell me it's because generally the bandwidth usage is heavy... videos playing and pics being loaded etc. I'm always sceptical of "reasons" as the cynic in me sees "excuses." However I do know there are some special concerns that we need to address as webmasters that mainstream does not. Which I'm not sure translate into more expensive hosting or not.

I sure do hope my site takes off and there's a viable reason to look further into hosting adult content. That's where the affiliate section will help me out tremendously.

As I understand, the most-often cited reason is heavy resource and bandwidth usage. This of course tells you a great deal about all those "large" non-adult hosting plans you get for cheap; they count on people not pushing traffic anywhere near the limits the package contains, and make the bulk of their income from recycling the unused overhed into cramming double or quadruple the amount of accounts the server could actually host. You are paying for it, but you're not expected to use what you pay for,

As far as our software goes, we are not moral or any other policy makers, and what you do with our tools is at your discretion. While it actually isn't currently noted in our licenses, I am personally a supporter of the free software concept; the first freedom being the right to use it in whichever way you choose to.