Marcus. A problem during installation.

Warning: file_get_contents(iWiccle v1.11 v1.11_110.sql) [function.file-get-contents]: failed to open stream: No such file or directory in /var/www/iwiccle/install/installer.php on line 380
Errors in the process!

Change the install.php to install. But no pictures module_header. Markus, you little hurried.

Manage language packs and select default site language.
⋅ All language folders in /templates are automatically detected. To create a new language pack, just copy in a new folder with the files and start editing.

Maybe /languages

When Markus is back, he will look into this. Hold tight =)

Tried a 'clean' install - new database and fresh upload of 1.11 - I got:

Warning: file_get_contents(iWiccle v1.11 v1.11_110.sql) [function.file-get-contents]: failed to open stream: No such file or directory in *************/install/installer.php on line 381
Errors in the process!

---

There were some errors in the database import (total 2 queries)!

---

⋅ You can try to refresh the page — the database will be written over. If the error persists, the next-easiest thing is taking the file and importing it manually.
⋅ You can then log in as "Admin / iWiccle v1.11 v1.11" and change your details from the Admin Panel. – just move the /tmp/config.php file into the root directory and delete or rename the install-folder.

 

• Query 0 (... failed! (Query was empty)

Tried refreshing the page - same message.

OK Keith. And so, looks like a template.

John rename iwiccle_111.sql in install folder to iWiccle v1.11 v1.11_110.sql. Or rename iWiccle v1.11 v1.11_110.sql in install.php line 381 to iwiccle_111.sql.

If I click "Log out".
I get the error:

Warning: Cookie names can not contain any of the following '=,; \t\r \013\014' in /var/www/iwiccle/index.php on line 120

Warning: Cannot modify header information - headers already sent by (output started at /var/www/iwiccle/index.php:120) in /var/www/iwiccle/index.php on line 123

I just wrote a longish reply that was eaten by IE6 on a public computer --- checking in on the road. I was afraid something silly might go wrong in all the rush to stick it up before heading out --- it was 7:55 AM or never. I'll tend to all this when I'm back at my machine later afternoon.

Sorry about the rushed release, I just wasn't into complaints over why it was late again... I suppose it would be prudent for me to stop making best-effort estimates on updates, we have enough rush as it is, and the last thing we need is more races to run.

Re your logout issue, this is the code:

$cookie_name = $core['init']['cookie_base']."_al";

if ($_SESSION['member']['member_id'] == 0 && !empty($_COOKIE[$cookie_name]))
{
 MemGlobal::process_autologin();
}

The cookie name then becomes iwiccle_al (for auto-login), or whatever else you set it to in the Admin CP. Double check that you do have a value there (under security IIRC) --- otherwise the cookie name would be _ai and start with an underscore...

Here's the problem: The cookie name got accidentally changed from "iwiccle" to "iWiccle 1.11", which is of course an invalid cookie name, at the last minute. My file header replacement before zipping it up ran amok and omitted the version number from the "search" line, thence your odd cookie name.

The SQL file actually took three hits: Admin default "status" in profile is "'iWiccle v1.11 v1.11 1.11 installed!'" --- so it's super duper installed if you got that far, and the default skin description also took an extra version number, which you can reset in skin settings. Not that it makes much of a difference.

The evils of global search & replace!

Thank you Litoz for your help.

I'm a bit of a 'newbie' with all this stuff. I renamed my upload 'Wiccle' and "went by the book". This is not usually a problem!

Now I'm totally confused!!!!!!!!!

I think it is best to wait for Markus to fix it up and then we will re-release v1.11 again with the few lines needed to rewrite the files correctly. If everyone can hold tight for a few hours, this will be done and then just download again where this will not be an issue.

Yes, I have just come back and reviewed the havoc that happened in the last 15 minutes before release. Damned search-replace went totally wild, froze and ran it over a couple of times without the relevant string suffix included! There are literally dozens of stray "iWiccle v1.11 v1.11" strings all over the place --- this bundle cannot be used. I have now put in place a notice on the download page.

Do not use v1.11 until I get all of the problems reverted. Should be done in a couple of hours time tops, I need to settle in and see what's going on. The bulk of it is/was easy to revert, but I need to be double sure before I put it up. (The file is currently unlinked.)

Keith Kililea "quote on quote " ( I think it is best to wait for Markus to fix it up and then we will re-release v1.11 again )

( that would be very un-professional if you ask me! )

v1.11A ( or what ever higher )

If any of you know when you fix bugs in a version it has to be eathier be a higher number or a higher letter then what it originally was for!

 Example:

( upgraded, hiccups,bugs, patches  in any of the fixed versions to come, never the same cause that will ONLY cause havok / chaos in the end for everyone! )

 

Solution:

( If today for example there were 3 patches for version v1.11 

 v.111a ( 1st patch "600am, 2009,august 14th" )

v.111b ( 2nd patch "900am, 2009, august 14th" )

v.111c ( 3rd patch " 1200pm, 2009, august 14th)

 

Yes I have seen these same mistakes done on another social software site where the software would be upgraded or patched but the nuber stayed the same and this caused problems for webmasters trying to figure out that there was 3 versions or 3 patches on that specific version in 1 version number!

 

This is a question of failed packaging. There never was any 1.11 you could run to begin with, the files were corrupted.

We don't generally update version without bumping the number, even if in my opinion same-day updates are no problem if there's a small goof to be fixed --- there's no need to bump the version number over that, though I hear what you're saying on bumping the version numbers. Of course it can't be a constant mini-tweak rally on the roll.

This packaging error was actually caused by a failed automatic file versioning to help us keep track of all file versions!

I will leave the decision to Markus on this one but thanks Technoman, your a good member to us as well to new members here. :)

Markus, calm down. Things tend to get out of control when working against the clock. I've had my share of crazy "search-replace" routines. You are doing your best, working off your back to give us a better product, and for free! Sure, I'm anxious to put my hand in this update but I can't expect you work 24-7 just to my convenience, can I? I really apreciate your dedication and I know (I think everyone should know) you're put your soul into this project. So, easy down, take a rest, refresh your mind and go to the review job at your own pace. When you finish, just tell us the good news ;)

BTW. There's any way we (the anxious audience) could help? I mean in general, not just now.

Life is about mistakes and nobody is perfect we all learn from eachothers own mistakes

Warning: file_get_contents please get rid of this php funtion in the code as we do not use this in any of the higher php 5.3 modules I notice this file_get_contents " error " in alot now adays in alot of software!

Thanks Iggy! We do have some plans and visions on how the community will grow and what people can do, and what we can do for them, but I will need to talk this over with Keith to see which way we can stretch, and when. We don't want to get people all rallied up for some huge community projects, and then run ourselves to the woods to code in peace and hiding to meet some deadlines, too.

Bug spotting and reporting is of course helpful and welcome, the more the merrier. Being around in forums to answer an odd question at an odd hour when nobody's around is always nice. Developing new skins and language packs is very cool. Building modifications and modules is great. And telling your friends about iWiccle is a moral obligation everyone should understand.

Technoman - file_get_contents()  is a rather central function. You only get an error if it fails in fetching the file --- and so you should --- just like with include, require and the rest.

1.11 is pretty much tidied up here. Doing repackaging and couple of test installs right about now.

Markus, Iggy rights. Sometimes it is necessary to have a rest. We in the country have a saying "More haste, less speed" - approximately so. But the criticism too is necessary, sometimes it helps. I now observe of one Russian project, there too there are similar problems. So terms it is terms, but a brain to overload it is not necessary.

Yes, tell me about it. Sometimes life goes faster than you do, there are times when just staying onboard is a full-time endeavor!

That said, 1.11 repack & patch is now available.

• http://www.wiccle.com/files/iwiccle_111.zip

More info in the news in a little bit. Please report how it kicks off --- I have just completed three seamless test installs on separate servers. Despite the sloppy entrée in the morning, a great deal of work and fixes went into this version.

Write Permissions
 "uploads/articles/thumbs" 2 times repeat.

Installation has passed normally.