I am constantly working on the wiki; addressing questions as fast as I can. "Session ID" was just "SID" a few minutes ago
Keep the questions comments coming
Might be a good idea to add to the e-Token section of the wiki what the 0.7.24 equivalent value is, ie.. if you set it to value 'X' are you actually changing anything once upgraded to 0.7.25.
Just want to be sure I don't balls it up... Other than that, upgrade has worked out a treat on my 'Test' site, thanks as always to the Dev team, who have all this to deal with along with the V.8 build, your efforts do not go un-noticed.
You only need to add this if you need to change the security level from default behaviour of 5 which is essentially setting e_Token to 0.7.24 security level.
Why though? It would allow people to quickly upgrade a test site. Its nice to see what files have been changed and e107 offered everything but the direct 0.7.24->0.7.25-r1
I do agree that if extra time was needed to create those but from what I understand there is a script that does this that is already in place.
There are already a couple of 'tweaks' in .svn post 0.7.25 rc1 which will hit the official release (or maybe an rc2 or rc3 if required) when that happens
Using the 'script' as far as I'm aware isn't so simple as it does more than just create a build so would need additional work.
Just to remind everyone, there was a long discussion about releasing 'buggy' versions and lots of 'whinging' about it, so the decision was taken to move to rc which are pre release versions for testing prior to a full release.
Should anyone without experience use rc versions on production sites?
Probably not, so not having simple upgrade versions discourages that.
Doesn't matter what the Dev team do though, someone, somewhere, isn't going to be happy and the current situation is the best compromise available in my personal opinion.
No doubt others will still disagree though...........
I completely understand I just don't understand why e107 has consistently produced them in the past and now doesn't. But looking at the other RCs it seems that they were all produced the same way. (without the direct upgrade path) Maybe I can help upgrade the current script?
And if you were referring to what I said by your commented C6Dave: I was talking about testing a production site, in a test environment. Example: Making a backup of your site, upgrading it and hosting it local to see if it works as expected with the current content.
It would surely help experienced and none experienced people test, its a convenience and not so much what the dev team is doing or not doing. I don't think anyone would have a problem with it being present.
It's not my decision and I wasn't referring to anyone's post, just making a general comment.
I have nothing to do with the builds and only limited members of the Dev Team does as far as I am aware
In the past Release Candidates were not available, you got a release, untested in a lot of environments which may have had unfound issues, the news release is here: [-link-]
Well, despite what we thought was some good testing of our 'stable' 0.7.23 prior to release, some users' installations became 'unstable' after upgrading. We believe most of these issues have now been corrected, but rather than simply making another official release, we will be introducing beta 'release candidates' into our release process.
In retrospect, this is what we should have done with 0.7.23 - so we've learned our lesson. From now on, the stable 0.7 will remain as such, and release candidates will be made available prior to any official release. This will allow us (and yourselves) to test the code more thoroughly and will also give official translators more time to update and validate their language-packs so they are ready in time for the next official release.
Has everyone forgotten about the level of forum posting that preceded it?
I haven't
If you feel that rc versions should also include an upgrade pack, put it in the ideas section, that's what it's there for guys.
I fixed it, by following the advice when i suffered issues from.24 rc2. I found the thread and it advised to rename the e107_handlers folder, and reupload it again. Done that, cleared browser cache, and the icons are back.
I suspect there can be redundant or relocated files in the tinymce directory which cause the problem - would be interesting if someone whose problems are fixed in this way could do a comparison.
I get this error message when upgrading [-link-] Fatal error: Call to undefined function: stripos() in /home/b/r/brembs.net/html/bjoern/class2.php on line 1721
I temporarily replaced class2.php from this release with an older version to keep the site running, but I'd appreciate any help on how to fix this issue. Thanks!
I temporarily replaced class2.php from this release with an older version to keep the site running, but I'd appreciate any help on how to fix this issue. Thanks!
It has been fixed already [-link-] However, I do advise you to upgrade to PHP5 asap
New problem. I upgraded a customers site yesterday, as i have had .5rc1 working fine on 2 of my own sites.
After the install everything was working as it should.
However customer put in a support ticket today to say his news post had gone missing.
When i visit the customers website [-link-] its not redirecting to news.php as it should. If i type in news.php at the end of the domain, website loads fine. If i type index.php at the end of domain its also not redirecting and the layout of the site is different to as it should be with news.php.
When i inspect the page i note a url within the docutype at the header of the index.php of [-link-] but editing the file manually its not there.
Themes and plugins havent changed overnight, so not sure whats going on here as everything worked the day b4. Ive manually inspected all files, and there seems to be nothing modified. I done a reinstall of rc1 again overwriting the files and problem still exists. Also if i activate the welcome message with a message it will not show. The customer the site relates to is a complete web "noob" and says he hasn't done or touched anything. So im curious as to how this problem has started. Ive checked status of the domain etc and theres no redirects, and no changes appeared to have been made. However seeing as i have reinstalled .5 rc1 again and potentially overwritten all the files some kind of exploit must exist somewhere. Ive run dbcheck and all the db tools, no issues found. Also cleared cache etc and again nothing found. 1 Thing i have noticed though is in admin area, the leave admin, settings and profile links have disapeared, using reline v1.0 stock template for admin, and use same for al my own sites and the info on the left has gone? but it was there yesterday. Ive also checked the htacess b4 the root of public_html and nothings changed. So not sure if we are dealing with a new exploit here, or some other kind of weird going ons.