HasOneComplexTableField not working in SilverStripe 3 beta 2

Frankieboy — Wed, 16 May 2012 16:21:46 +1200

HasOneComplexTableField is no longer working in SilverStripe 3 as the warning is shown up "TableListField requires FRAMEWORK_DIR to be sapphire."

I attempted to use GridField as an alternative but it was not working either. Does anyone have an idea what is the alternative for HasOneCompleTableField in SilverStripe 3?

P.S: Certainly, I can use GridField for 1-to-many and many-to-many relationship but not for 1-to-1 relationship.

Thanks

Posted to: HasOneComplexTableField not working in SilverStripe 3 beta 2 | Show Thread | Post Reply

Search not working in Silverstripe 3 beta 2

Frankieboy — Mon, 14 May 2012 10:43:22 +1200

Hi,

The search function is not working. It either crashes the Apache server or return no result. Have anyone got this experience ?

P.S: What I have done is
-set FulltextSearchable::enable();
-added $SearchForm to Page.ss
-added Page_results.ss to theme layout
-had /dev/build?flush=all

Posted to: Search not working in Silverstripe 3 beta 2 | Show Thread | Post Reply

Re: SilverStripe 3.0.0 - Unable to Add Fields

PeMu — Wed, 09 May 2012 08:31:36 +1200

Hi Lukereative and Garrett,

I also figured this out after posting but didn't quite get round to updating - so that make three of us. Glad the answer is here for others now though as this was the first result in my search for answers.

I'm very new to Silverstripe and have made the 'interesting' decision to try out SS 3.0 by following tutorials for previous versions so may see you around on the forum again in the future.

Peter

Posted to: SilverStripe 3.0.0 - Unable to Add Fields | Show Thread | Post Reply

Re: SilverStripe 3.0.0 - Unable to Add Fields

Garrett — Wed, 09 May 2012 02:10:47 +1200

That more than helps, it solves ;) I figured this out just like you a long time ago though but thanks anyways for replying!

//Garrett

Posted to: SilverStripe 3.0.0 - Unable to Add Fields | Show Thread | Post Reply

Re: SilverStripe 3.0.0 - Unable to Add Fields

Lukereative — Tue, 08 May 2012 15:58:12 +1200

I had this problem too and forgot to post my fix.

To add fields to the main tab -
Instead of

$fields->addFieldToTab('Root.Content.Main'

Just remove the .Content part

$fields->addFieldToTab('Root.Main'

Similarly to add fields to your own tab -
Instead of

$fields->addFieldToTab('Root.Content.MyTab'

Just remove the .Content part

$fields->addFieldToTab('Root.MyTab'

Hope that helps.

Posted to: SilverStripe 3.0.0 - Unable to Add Fields | Show Thread | Post Reply

Re: SilverStripe 3.0.0 - Unable to Add Fields

PeMu — Sun, 06 May 2012 21:30:40 +1200

Hi Garrett,

I'm just wondering if you ever figured this out? I'm also scratching my head on this one.

Peter

Posted to: SilverStripe 3.0.0 - Unable to Add Fields | Show Thread | Post Reply

Re: Upgrading SilverStripe 2.x to 3.x

swaiba — Tue, 24 Apr 2012 04:44:19 +1200

I think you might want to review the developer gogle group where most of the discussion is. For eaxmple one of the main projects for the GSOC is the module directory and how that can be handled in the future. Currently there is nothing that will address the module situation.

I'm suprised that the link didn't cover the upgrade stuff as it covers each upgrade within 2.x fairly well and then in the case of a 2.4.x to 3.0.0.beta it is so comprhensive I was really impressed. Ingo has mentioned several times that upgrading is going to be painless in the form of using modules to fill in depreciated/removed functinoality (even the CTF!) but it is still early days - I don't expect to address any of this fro about 6 months - probably 3.1.x - after it is extermely stable.

Posted to: Upgrading SilverStripe 2.x to 3.x | Show Thread | Post Reply

Re: Upgrading SilverStripe 2.x to 3.x

mrcheeseburger — Tue, 24 Apr 2012 04:27:04 +1200

Thanks Barry,

Thats really useful infomation and I had stumbled across that particular changelog.

Although this doesn't directly answer my question, let me rephrase it slightly....

Assuming we have reached a bona fide release candidate for 3.x later in the year, would there be an approved migration method published or are site owners going to have to go through the process of trawling changelogs to ensure they get 3.x to a fully working state post upgrade.
It would also be nice to have someone put together a module compatibility matrix for the most widely used standard modules available to download.

I appreciate your valuable feedback!

regards
MrC

Posted to: Upgrading SilverStripe 2.x to 3.x | Show Thread | Post Reply

Re: Upgrading SilverStripe 2.x to 3.x

swaiba — Tue, 24 Apr 2012 02:33:13 +1200

mrcheesburger

there currently is no "supported" version to upgrade to, so there are no supported docs

however there is an extermely comprehensive amoutn of information on upgrading for the beta releases right here... http://doc.silverstripe.org/sapphire/en/trunk/changelogs/3.0.0

Posted to: Upgrading SilverStripe 2.x to 3.x | Show Thread | Post Reply

Upgrading SilverStripe 2.x to 3.x

mrcheeseburger — Tue, 24 Apr 2012 01:02:18 +1200

Can anyone give an indication if there will be a supported upgrade path for users with site on 2.x wanting to upgrade to 3.x
e.g. list of pre-reqs, upgrade scripts etc. module compatibility etc. etc....

I'd appreciate some information on this if there is anything on the radar expected in the not too distant future.

regards
MrC

Posted to: Upgrading SilverStripe 2.x to 3.x | Show Thread | Post Reply

Re: Silverstripe 3.0 beta1 custom Loginform

Andre — Fri, 13 Apr 2012 09:19:23 +1200

Sorry, there is no Bug and nothing is going wrong. I just forgot to empty the silverstripe-cache folder.

Posted to: Silverstripe 3.0 beta1 custom Loginform | Show Thread | Post Reply

Re: Silverstripe 3.0 beta1 custom Loginform

Andre — Fri, 13 Apr 2012 08:54:37 +1200

I have tried now with the Full Silverstripe Framework (including the cms) and still have the same error.

The templates/Layout/Security_login.ss file sits within my module Directory not within my themes Directory (as it was possible in Silverstripe 2.4.x).

Has there something changed or is it a bug?

Posted to: Silverstripe 3.0 beta1 custom Loginform | Show Thread | Post Reply

Silverstripe 3.0 beta1 custom Loginform

Andre — Thu, 12 Apr 2012 12:17:58 +1200

Hi,

I installed the Silverstripe-framework-v3.0.0-beta-1 Package (not the CMS Package), to start a new Project and migrate some of my existing modules.

I added a custom templates/Layout/Security_login.ss File to one of my Modules, to have a custom Login Template, but this template doesn't show up.

Has there something changed within the customising of Login?

Posted to: Silverstripe 3.0 beta1 custom Loginform | Show Thread | Post Reply

Re: 2.2.2 Upgrade to 2.4.7

Willr — Mon, 09 Apr 2012 20:42:14 +1200

Another solution is to look for the string (using 'Find in project' or whatever you have in your text editor) for 'extraDBFields'. That will point out which one of your modules is out of date.

Posted to: 2.2.2 Upgrade to 2.4.7 | Show Thread | Post Reply

Re: 2.2.2 Upgrade to 2.4.7

Kiwipearls — Mon, 09 Apr 2012 10:57:57 +1200

Hi there,

Thanks for looking for me.

All modules were working fine with 2.4.7 on the test server and all other modules that were not needed were deleted. ie they had JSparty.

I upgraded my test server from 2.4.6 to 2.4.7 to test them all out beforehand - so that is confusing. And I just checked my servers erro log and the log file is 0Bytes.

I guess what I will do is a clean install and cut n paste data back in. That is the only way I can think of with my experience level being new to SilverStripe to get the site looking and performing exactly as my server.

I will get her to contact her webhosts for me tomorrow..or offer her webhosting with my hosting company. As that would also make things a lot easier.

Posted to: 2.2.2 Upgrade to 2.4.7 | Show Thread | Post Reply

Re: 2.2.2 Upgrade to 2.4.7

Willr — Mon, 09 Apr 2012 09:54:55 +1200

Going through that a couple things pop up

- PHP Notice: DataObjectDecorator::extraDBFields() is deprecated. Please use extraStatics() instead

That would indicate that one of your modules is out of date with 2.4.7. You will need to update that module

-PHP Fatal error: Allowed memory size of 33554432 bytes exhausted

Your host is running out of memory (32mb). SilverStripe recommends 48mb at least to run, I suggest for an average medium site if you're dealing with large images (say a gallery) you'll need more around 128mb.

Posted to: 2.2.2 Upgrade to 2.4.7 | Show Thread | Post Reply

Re: 2.2.2 Upgrade to 2.4.7

Kiwipearls — Mon, 09 Apr 2012 09:28:58 +1200

Ok I found my error logs and it is gobbly gook to me, but I know for someone out there it makes perfect sense.

I thank you in advance for going through the file - I've taken it from the day I upgraded, but there were many errors even before I touched anything.

I tried putting the site in to dev mode - but didn't know where to look for errors.

I also have to wait for my neighbour to come back from holiday because I need access to her webhosts control panel as some files in assets do not have the right file permissions and I get CMOD errors with my ftp client.

Posted to: 2.2.2 Upgrade to 2.4.7 | Show Thread | Post Reply

Re: 2.2.2 Upgrade to 2.4.7

Kiwipearls — Fri, 06 Apr 2012 09:22:45 +1200

Hi Willr

Thanks so much for your reply.

I had 2.4.7 and all modules on a test server (online)- then when that looked sweet and functioned, upgraded the live server to 2.4.7 from 2.2.2 replacing all modules.

this test server was just testing the theme and modules not the whole database...so maybe if I imported the DB I would not have had this problem?

I will put it in dev mode after the long weekend or when I get a free moment to see what errors it is spitting out exactly - if I look in the right place.

I don't know how to run a developer site on my computer which is why I set it up on my test domain online. I am thinking I got in over my head, but I suppose sometimes you don't learn if not thrown in the deepend.

Posted to: 2.2.2 Upgrade to 2.4.7 | Show Thread | Post Reply

Re: 2.2.2 Upgrade to 2.4.7

Willr — Thu, 05 Apr 2012 22:48:32 +1200

That error message is a lot of smoke and really you just want to get down to the fire. (Internal Server Error) indicates that you're running in live mode, swap the site to dev mode (or look at your php error logs) and you'll get a actual error message.

2.2 -> 2.4 is a significant upgrade (roughly 2 years) so make sure all the modules you have are up to date as well.

You shouldn't update any live site directly for this reason. Download the live db / assets to your computer and setup a dev version to fix any bugs.

Posted to: 2.2.2 Upgrade to 2.4.7 | Show Thread | Post Reply

2.2.2 Upgrade to 2.4.7

Kiwipearls — Thu, 05 Apr 2012 14:31:31 +1200

I have 2.4.7 installed on my test server with working modules.

Live server was running silver stripe 2.2.2 and I upgraded everything to 2.4.7. I followed silver stripes upgrade instructions.

Everything appears to have gone right. Normal pages look fine, save fine, can be edited fine..

Except...

Ecommerce module, when adding images to product group pages - it will not save the page.

In Files and Images I cannot look for new files.

It is not detecting some folders in the file manager that are in the assets directory. Especially when it comes to re-sampled images.

When I check for errors in Google chrome I get:

http://www.breeartze.co.nz/admin/EditorToolbar/ImageForm?action_callfieldmethod=1&fieldName=FolderImages&ajax=1&methodName=getimages&folderID=&searchText=&cacheKillerDate=1333592570891&cacheKillerRand=6605Failed to load resource: the server responded with a status of 500 (Internal Server Error)
Refused to set unsafe header "Connection"
2event.layerX and event.layerY are broken and deprecated in WebKit. They will be removed from the engine in the near future.
http://www.breeartze.co.nz/admin/EditFormFailed to load resource: the server responded with a status of 500 (Internal Server Error)
2Refused to set unsafe header "Connection"
2event.layerX and event.layerY are broken and deprecated in WebKit. They will be removed from the engine in the near future.
http://www.breeartze.co.nz/admin/EditFormFailed to load resource: the server responded with a status of 500 (Internal Server Error)

I have absolutely no idea what this means or how to fix this. I really do hope someone has a solution.

My only other option is to delete the whole DB and reinstall fresh - then enter in my pages and products all over again. Surely there must be a way that is easier and better?

I've upgraded this website for a friend, and currently have had to put their site into construction mode while I figure out how what to do. This is a live business so I don't want it to be in construction mode for too long.

I very eagerly look forward to someone's assistance on this.

Posted to: 2.2.2 Upgrade to 2.4.7 | Show Thread | Post Reply

Re: Upgrading to 3.0 beta - Guide

simon_w — Thu, 22 Mar 2012 09:30:39 +1300

This is a known bug caused by using Director::set_dev_servers(), which has been deprecated in favour of _ss_environment.php. It's been deprecated because relying on a user-supplied value for enabling dev mode is somewhat dangerous.

Posted to: Upgrading to 3.0 beta - Guide | Show Thread | Post Reply

Upgrading to 3.0 beta - Guide

njprrogers — Thu, 22 Mar 2012 07:24:36 +1300

Hi,

I'm trying to upgrade my 2.4.2 version of Silverstripe to version 3.0 beta. I'm excited to see how much I need to do to get myself up and running.

I've failed to find any upgrade notes or anything in the changelog to indicate how to go about the upgrade. Is there any information available on how to go about this?

Without guidance, I've just gone ahead and downloaded version 3.0 and replaced the themes folder and my page types etc. (60 of them!). I've taken the config file from 3.0 and added my setup.

Unfortunatlely, I'm getting an error probably caused by a loop.

Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 523800 bytes) in /Applications/MAMP/htdocs/SilverStripe3b1/sapphire/dev/Deprecation.php on line 818

I've expanded the memory to a gig, and Deprecation.php only has 180 odd lines so the message is not helping me.

Has anyone gone through this process? Help!

Thanks,

Nick

Posted to: Upgrading to 3.0 beta - Guide | Show Thread | Post Reply

Re: userdefinedform on 2.4 stable

Flaex — Fri, 16 Mar 2012 03:33:24 +1300

I worked with SS and its modules for a couple of years and they always run cool and smooth, yesterday for the first time i had the memory fatal error. Thankfully, there's a community who always want to help with advices and knowledge.

Thank you guys, we're improving the best CMS ever created!

Posted to: userdefinedform on 2.4 stable | Show Thread | Post Reply

Re: Site Tree Flakiness after upgrade to 2.4.5

bhowell — Fri, 16 Mar 2012 00:49:45 +1300

Hi JC,

We still have the same problem. I gave up trying as we are going with another CMS solution as part of a site re-design. But if you find a solution do share.

Posted to: Site Tree Flakiness after upgrade to 2.4.5 | Show Thread | Post Reply

Re: Site Tree Flakiness after upgrade to 2.4.5

JC — Wed, 14 Mar 2012 23:57:14 +1300

Hi bhowell,

Just wondering if this issue was ever solved? I am experiencing a very similar issue after upgrading.

Cheers,

Posted to: Site Tree Flakiness after upgrade to 2.4.5 | Show Thread | Post Reply

Re: Migrating Windows, SilverStripe 2.4.2 and MySQL -> SQL Server?

wilsonStaff — Thu, 08 Mar 2012 04:30:15 +1300

Sorry to hijack.

Sean, i have the exact opposite problem.

Weve started the site on IIs SQL and need to migrate to Apache mySQL.

Can someone successfully convert an SQL DB to mySQL DB?

If so, how to do that?

Any help appreciated.

Thanks!

Posted to: Migrating Windows, SilverStripe 2.4.2 and MySQL -> SQL Server? | Show Thread | Post Reply

Re: Upgrade TinyMCE

Lucas — Wed, 07 Mar 2012 13:01:32 +1300

Well, not sure of your specific problem, but when nothing else works, try this process:

1.Find your silverstripe cache directory. On my machine it's in /tmp/silverstripe-cache-websitename
Remove all the contents beneath this directory.

2. Visit YOUR_SITE_URL/dev/build?flush=all

3. Close the page and clear your browser cache

4. Reload the site and see if anything is better.

Posted to: Upgrade TinyMCE | Show Thread | Post Reply

Re: Upgrade TinyMCE

scottfromoz — Wed, 07 Mar 2012 12:07:44 +1300

I am trying to get more access to html coding via ss. I have tried adding the full list to valid_elements but it did not make any difference, I tried setting to advanced and there was no change in the buttons I saw. I have even now just copied all the files from the latest version of tinymce over the top of my old files, and still there is no change (the buttons all look like the old buttons). Is there some re-compiling step I am missing?

Posted to: Upgrade TinyMCE | Show Thread | Post Reply

Re: Upgrade TinyMCE

siannaDesttiny — Fri, 02 Mar 2012 20:10:54 +1300

wonderful.

Posted to: Upgrade TinyMCE | Show Thread | Post Reply

Re: Cached method deprecated in 2.4.7?

tksano — Thu, 01 Mar 2012 00:16:21 +1300

Oops, I remembered that I applied the patch a while ago. I unintentionally overwrote that file with the 2.4.7 upgrade!

Thank you for reminding me of it, JonoM!

Posted to: Cached method deprecated in 2.4.7? | Show Thread | Post Reply

Re: Cached method deprecated in 2.4.7?

JonoM — Wed, 29 Feb 2012 17:21:29 +1300

There is a bug that causes this - you can find a patch for ViewableData.php here: http://open.silverstripe.org/ticket/6241 although it's strange that you weren't having a problem with 2.4.6 as this bug has been around for a while I think?

Posted to: Cached method deprecated in 2.4.7? | Show Thread | Post Reply

Cached method deprecated in 2.4.7?

tksano — Wed, 29 Feb 2012 16:27:26 +1300

Hi everyone,

I have an issue with upgrading our silverstripe install from 2.4.6 to 2.4.7.

I use cached methods, which have an underscore (_) prepended to their names, in my code for performance improvement. However, after I upgraded my site to 2.4.7, silverstripe started to produce errors as shown below:

Warning: implode() [function.implode]: Invalid arguments passed
At line 365 in /***/silverstripe/sapphire/core/ViewableData.php

Or,

Warning: Illegal offset type
At line 385 in /***/silverstripe/sapphire/core/ViewableData.php

Is this expected behaviour? Is cached method or call deprecated in 2.4.7?

Thanks,

Posted to: Cached method deprecated in 2.4.7? | Show Thread | Post Reply

Re: Upgrade TinyMCE

Lucas — Sun, 26 Feb 2012 13:12:57 +1300

Have a look at what Aram says. I found this worked for me.

Also I was able to create a custom plugin, based on copying the example plugin (sapphire/thirdparty/tinymce/plugins/example), and modifying with examples found on the tinymce site, here

Then I enabled my plugin and added it's button, using what Aram describes.

Good luck!

- Luke

Posted to: Upgrade TinyMCE | Show Thread | Post Reply

Re: version number in 2.4.6 CMS missing

Ingo — Thu, 02 Feb 2012 07:02:18 +1300

Sorry about that. I've now added this to the build file in https://github.com/silverstripe/silverstripe-installer/commit/44409c75ac1bdd75a857db4ea3583ede1b6b0b3f which ensures that the next release contains this information again.

Also changed the sapphire/cms logic accordingly: https://github.com/silverstripe/sapphire/commit/d261f4406afb732280f20c30c33fba2703abe0e8 - This change is applied to all maintained releases (back to 2.3), as we're no longer building any of those via "svn export".

Posted to: version number in 2.4.6 CMS missing | Show Thread | Post Reply

Re: version number in 2.4.6 CMS missing

ChubChub — Thu, 02 Feb 2012 04:00:15 +1300

Hey Ingo, did I miss something? the new 2.4.7 didn't have it either - is there a safe place I can add it myself? What do you recommend? It's so nice to have the version there...
Thanks in advance.

Posted to: version number in 2.4.6 CMS missing | Show Thread | Post Reply

Re: Upgrade TinyMCE

zigojacko — Thu, 02 Feb 2012 02:39:38 +1300

Altering either HtmlEditorField.php and HtmlEditorConfig.php makes no difference to the TinyMCE buttons in the CMS for me.

Adding something such as HtmlEditorConfig::get('cms')->addButtonsToLine(1, 'hr,removeformat,visualaid'); for example, does work, but only for certain buttons.

I have literally tried to add an image button to TinyMCE via about 30 different approaches now and I'm getting extremely frustrated. I've just inherited the development of a client after another company have made alterations.

Can anyone kindly advise on the how the hell I'm suppose to make changes to TinyMCE please?

In the back office of clients site, version specifies Simple CMS 2.3.3

Thanks in advance

Posted to: Upgrade TinyMCE | Show Thread | Post Reply

Tinymce Upgrade with HTMLTextField problems in IE9

midoriberlin — Sat, 31 Dec 2011 04:56:01 +1300

Hello all,

I'm posting this here in the hopes of a) helping someone else who's run into this and b) trying to find a more elegant solution than the one I came up with myself.

In testing a Silverstripe application I'm working on I noticed that using HTMLTextField with Internet Explorer 9 is basically impossible as it stands. The core of my application relies on people being able to manage and upload text content through an editor (this seems like a fairly common core, non-negotiable piece of functionality for a lot of applications). Problems I was getting was the textarea becoming uneditable after content was put into it and automatically clearing on submit so that the form could never be completed. Showstoppers in other words.

Everything fine and dandy in IE8 but obviously anyone on a relatively new PC is going to be increasingly on 9 by default so it's something I have to accomodate. Started looking into fixes and things suddenly started looking very messy indeed. Options I considered:

i) Put new version of Tinymce in Sapphire - Easy enough to drop new files in there and seemed to work on frontend but butchered the admin, as several previous posters pointed out it might do.

ii) Make allowances for the various javascript erros IE9 triggers - This chap seemed to have worked through the various incompatibilities and documented the process at http://daveymorris.co.uk/web-development/tinymce-and-internet-explorer-9-fix-again/ but frankly that looked like a lot of work to go through.

iii) Quick and dirty - In the end I just went for forcing the browser to think it's actually IE8 by adding <meta http-equiv="X-UA-Compatible" content="IE=8" > to the head which I *think* seems to have fixed the problems.

So, the fix above (number iii) isn't by any means extensively tested and I have a nasty feeling it will screw something else up but it seems to be working for now. Seems very far from ideal though.

My main question is does anyone have a straightforward way of upgrading Tinymce without knocking out half the admin? If not, is there any date on when this might go into some version of core?

Loving Silverstripe to bits generally, massively appreciative of the framework and all the work that's gone into it but this really seems like something that will cause a lot of people problems and should be gotten to as soon as possible.

Found what seemed to be a good overview of the current situation here - http://www.silverstripe.org/general-questions/show/18560

I'd be interested if anyone has had similar problems and has tried similar or different solutions and how they got on.

All the best,

Andrew

Posted to: Tinymce Upgrade with HTMLTextField problems in IE9 | Show Thread | Post Reply

Re: Version not showing after upgrade

smares — Tue, 20 Dec 2011 20:23:25 +1300

http://www.silverstripe.org/upgrading-silverstripe/show/18344

Posted to: Version not showing after upgrade | Show Thread | Post Reply

Re: Version not showing after upgrade

RichMcNabb — Wed, 14 Dec 2011 09:16:18 +1300

Seems to be a common fault.

When I log into SS's demo site (http://demo.silverstripe.org/) the version number is not displayed either.

Posted to: Version not showing after upgrade | Show Thread | Post Reply

Re: Version not showing after upgrade

fiord — Wed, 14 Dec 2011 09:13:24 +1300

I have same trouble
when I update SS from 2_4_2 to 2_4_6
oll work well, but not show SS version in admin
RichMcNabb, which the localization admin panel using?

Posted to: Version not showing after upgrade | Show Thread | Post Reply

Version not showing after upgrade

RichMcNabb — Thu, 01 Dec 2011 16:20:50 +1300

Hi there,

I have just upgrade SS from 2.4.0 to 2.4.6 by using the following steps:

1. Deleting the cms and sapphire directories
2. Copying the new cms and sapphire directories from the downloaded 2.4.6 folder
3. Completing a http://www.mysite.com/dev/build/?flush=1 to rebuild the database.

Everything seems to be fine however in the CMS down the bottom left where the version is displayed it is blank.

Any ideas? Should I be worried?

Cheers!

- Rich

Posted to: Version not showing after upgrade | Show Thread | Post Reply

Re: Site Tree Flakiness after upgrade to 2.4.5

Howard — Sat, 29 Oct 2011 10:43:09 +1300

That's odd - havent experienced it myself.

Perhaps a file got corrupted but either way you could try updating to 2.4.6 and see if that resolves the issue.

Howard

Posted to: Site Tree Flakiness after upgrade to 2.4.5 | Show Thread | Post Reply

Re: Site Tree Flakiness after upgrade to 2.4.5

Howard — Sat, 29 Oct 2011 10:43:08 +1300

That's odd - havent experienced it myself.

Perhaps a file got corrupted but either way you could try updating to 2.4.6 and see if that resolves the issue.

Howard

Posted to: Site Tree Flakiness after upgrade to 2.4.5 | Show Thread | Post Reply

Re: upgrade 2.4.6 googlesitemaps missing

WorkingSolution — Thu, 27 Oct 2011 18:13:56 +1300

a litte note in file "UPGRADE" would be fine ;)

cite: " - With these folders: cms, sapphire, googlesitemaps
- Delete your existing folders
- Extract and replace folders from your download (leave modules
and your custom directories alone)..."

so I was confused while upgrading too

Posted to: upgrade 2.4.6 googlesitemaps missing | Show Thread | Post Reply

Re: version number in 2.4.6 CMS missing

Ingo — Tue, 25 Oct 2011 20:54:26 +1300

Thats an oversight on our first release from git instead of SVN, where these magic strings are automatically replaced on "svn export". Will be fixed with the next release, sorry about that!

Posted to: version number in 2.4.6 CMS missing | Show Thread | Post Reply

Re: version number in 2.4.6 CMS missing

lx — Tue, 25 Oct 2011 06:49:37 +1300

does anyone know where to insert the missing version number?
The dashboard module shows that a never version (2.4.5) is available.

---

i edited 2 files:
Now the dashboard doesnt inform me, that a "never" 2.4.5 is available.

sapphire/silverstripe_version
$URL: http://svn.silverstripe.com/open/modules/sapphire/tags/2.4.6/silverstripe_version $

cms/silverstripe_version:
$URL: http://svn.silverstripe.com/open/modules/sapphire/tags/2.4.6/silverstripe_version $

Posted to: version number in 2.4.6 CMS missing | Show Thread | Post Reply

Re: version number in 2.4.6 CMS missing

Platypus — Fri, 21 Oct 2011 12:14:37 +1300

Yes, the version number is missing here too. (Upgraded from 2.4.5. to 2.4.6).

Ok, in sapphire/silverstripe_version I only find:

$URL$

In SS 2.4.5 the line reads:

$URL: http://svn.silverstripe.com/open/modules/sapphire/tags/2.4.5/silverstripe_version $

Posted to: version number in 2.4.6 CMS missing | Show Thread | Post Reply

Re: upgrade 2.4.6 googlesitemaps missing

Willr — Thu, 20 Oct 2011 20:38:28 +1300

sitemaps will now be distributed as a separate module - https://github.com/silverstripe-labs/silverstripe-googlesitemaps.

Posted to: upgrade 2.4.6 googlesitemaps missing | Show Thread | Post Reply

version number in 2.4.6 CMS missing

freakout — Thu, 20 Oct 2011 08:22:01 +1300

after upgrade to 2.4.6 no more display of version number in backend bottom line - shows only "SilverStripe CMS" - but no version number as in all versions before.

Posted to: version number in 2.4.6 CMS missing | Show Thread | Post Reply

Re: upgrade 2.4.6 googlesitemaps missing

Smurkas — Thu, 20 Oct 2011 01:01:02 +1300

I don't know about the UPGRADING file but since there hasn't been any changes to the module and the whole module is in the googlesitemaps folder it doesn't really affect the upgrading process. It's only the core system you're replacing.

Posted to: upgrade 2.4.6 googlesitemaps missing | Show Thread | Post Reply