Forum posts to 'Upgrading SilverStripe'

Re: Upgrading jQuery version

chingochango — Thu, 18 Mar 2010 17:14:52 +1300

Hi Jason,

A good place to keep up on the news for Silverstripe is on twitter.

There is a quite a frequent mention of Silverstripe in the twitterverse. @Silverstripe is the twitter account for Silverstripe and there are quite a few members here that are on twitter as well (Uncle Cheese, Mo, Wiilr, Ingo, Hamish...) I recommend it. Grab TweetDeck http://www.tweetdeck.com - and you will be rolling

My account in Twitter is @silverstriper if you jump on there.

Posted to: Upgrading jQuery version Show Thread | Post Reply

Re: Upgrading jQuery version

Judge — Thu, 18 Mar 2010 12:13:04 +1300

Good move

I had no idea beta 2 was out already. I'm guessing that I'm not looking in the right place...?

-- Jason

Posted to: Upgrading jQuery version Show Thread | Post Reply

Re: Upgrading jQuery version

Willr — Thu, 18 Mar 2010 12:06:16 +1300

Check out the 2.4b2. Upgraded to jQuery 1.4.2.

Posted to: Upgrading jQuery version Show Thread | Post Reply

Upgrading jQuery version

Judge — Thu, 18 Mar 2010 02:27:15 +1300

I was wondering if there are any plans to bring the jQuery version in SS up to a more recent version? In the 2.4 beta it is at version 1.2.6, which is now pretty old. It does not include a lot of the live() features (except through a separate plugin), something that is becoming increasingly important with heavy AJAX loading of page areas.

If I were to upgrade my own version (looking at the 2.4 beta) where would I need to change it? sapphire/thirdparty/jquery/jquery-packed.js, or is it sill stuffed into another SS "base.js" file with prototype like for SS 2.3?

-- Jason

Posted to: Upgrading jQuery version Show Thread | Post Reply

Re: Charging clients for upgrades?

banal — Mon, 15 Mar 2010 11:34:36 +1300

He's just a spammer. They usually don't care about hijacking threads do they? But yeah.. it's kinda annoying.

Posted to: Charging clients for upgrades? Show Thread | Post Reply

Re: Charging clients for upgrades?

Double-A-Ron — Mon, 15 Mar 2010 10:07:31 +1300

Please don't hijack threads. You only decrease your chances of finding help anyway, since this thread has absolutely nothing to do with what you are asking. So someone who may be able to help will completely miss it.

Start a new thread.

Posted to: Charging clients for upgrades? Show Thread | Post Reply

Re: Charging clients for upgrades?

adamgilly — Sun, 14 Mar 2010 00:29:13 +1300

I need a calendar with events or "products" displaying on each day, with a way to select/deselect to the cart. I need the cart to also look like a calendar. Email me at onmountain at swatch watches if anyone has done anything like this.I am trying to do the same which you were doing,can you let me know whether you have achieved the target?if you are able to do it can you share the code or modification
Thanks

Posted to: Charging clients for upgrades? Show Thread | Post Reply

Re: Upgrade 2.3.3 to 2.3.6 template problems

arthurdent — Mon, 01 Mar 2010 20:44:20 +1300

Upon re-reading my post one thing's pretty obvious - line 175 generates a list of things that Sapphire wants but can't find. Trouble is, I don't know why it wants them at this stage? Weren't they there under 2.3.3? What are they?

Any assistance appreciated!

Posted to: Upgrade 2.3.3 to 2.3.6 template problems Show Thread | Post Reply

Upgrade 2.3.3 to 2.3.6 template problems

arthurdent — Mon, 01 Mar 2010 17:16:58 +1300

Hi, hope someone can offer me some advice. I just installed a clean copy of SS 2.3.6 onto a development server. Tested using the Blackcandy theme and then updated and uploaded my _config.php file and the theme that I had designed for my client that HAD been working under SS 2.3.3. Fired the site up and got the following screen:

Source

166                $this->chosenTemplates['main'] = $this->chosenTemplates[$templateFolder];
167                unset($this->chosenTemplates[$templateFolder]);
168             }
169          }
170
171          if(isset($_GET['debug_request'])) Debug::message("Final template selections made: " . var_export($this->chosenTemplates, true));
172
173       }
174
175       if(!$this->chosenTemplates) user_error("None of these templates can be found: ". implode(".ss, ", $templateList) . ".ss", E_USER_WARNING);
176
177       parent::__construct();
178    }
179
180    /**
181     * Returns true if at least one of the listed templates exists

Trace

* None of these templates can be found: Page.ss, ContentController.ss
Line 175 of SSViewer.php
* SSViewer->__construct(Array)
Line 305 of Controller.php
* Controller->getViewer(index)
Line 172 of Controller.php
* Controller->handleAction(HTTPRequest)
Line 129 of RequestHandler.php
* RequestHandler->handleRequest(HTTPRequest)
Line 119 of Controller.php
* Controller->handleRequest(HTTPRequest)
Line 29 of ModelAsController.php
* ModelAsController->handleRequest(HTTPRequest)
Line 44 of RootURLController.php
* RootURLController->handleRequest(HTTPRequest)
Line 280 of Director.php
* Director::handleRequest(HTTPRequest,Session)
Line 121 of Director.php
* Director::direct(/)
Line 118 of main.php

Apparently it's something to do with line 175 - can anybody tell me what the zark is going on?

Posted to: Upgrade 2.3.3 to 2.3.6 template problems Show Thread | Post Reply

Userforms v 0.2.1 doesn't work with SS 2.3.5

Oyster — Sun, 28 Feb 2010 11:44:42 +1300

I am not really sure if my problem is an upgrading issue, or a modules issue.

But:

My userforms were working smoothly with SS 2.3.3. After upgrading to 2.3.5 - directly, not via 2.3.4, my userforms stopped working. Symptoms: In back end, when trying to make new form-fileds, nothing happens. In front end (on live userfrom pages, created before upgrading) the forms looks all right, but doesn't perform. That is: Nothing happens when pressing "Send"-button.

Anyone else had this problem?

Can you guys help out? I'm quite stuck, and really don't know even where to start....

Tried to install unstable new versions of userforms (trunk r98906), without sucess.

Posted to: Userforms v 0.2.1 doesn't work with SS 2.3.5 Show Thread | Post Reply

Files and Images; able to upload, not able to view...Maybe a bug?

Mohammed — Fri, 26 Feb 2010 13:03:33 +1300

Hi guys,

I'm not too sure if this is a bug or not...

When I upload a PDF or an image via Silverstripe's "File and Images" tab, the file uploads just fine. The problem is that the uploaded files permission somehow gets set to 600; hence the user cannot view the PDF/image. This is occurring with version 2.3.6.

On another server I have version 2.3.5 installed. I don't have this problem using that version/server.

The "assets" folder's permission on both servers are set to 777. Is anyone else having this issue? Is there anything I can do to fix this issue?

Posted to: Files and Images; able to upload, not able to view...Maybe a bug? Show Thread | Post Reply

Re: 2.4.0 Beta Upgrade Errors

pingu — Wed, 24 Feb 2010 11:31:28 +1300

Okay, as it turns out I just had to empty the silverstripe-cache directory, and all is well.
Woops.

Posted to: 2.4.0 Beta Upgrade Errors Show Thread | Post Reply

2.4.0 Beta Upgrade Errors

pingu — Wed, 24 Feb 2010 10:46:52 +1300

Hi,

I'm trying to upgrade a local version of a website from 2.3.1 -> 2.4 Beta, and I'm getting some errors.
I've deleted the cms and sapphire folders and overwritten with what's included in the 2.4 package, but the error I'm getting is:
Fatal error: Class 'SS_Database' not found in \sapphire\core\model\MySQLDatabase.php on line 10

If I then proceed to copy over the googlesitemaps folder, I initially get a few more errors, which later disappear:

Notice: Undefined index: GoogleSitemapDecorator in \sapphire\core\ManifestBuilder.php on line 447

Warning: There are two files both containing the same class: '/googlesitemaps/code/GoogleSitemap.php' and ''. This might mean that the wrong code is being used. in \sapphire\core\ManifestBuilder.php on line 449

Notice: Undefined index: GoogleSitemap in \sapphire\core\ManifestBuilder.php on line 447

Notice: Undefined index: GoogleSitemapDecorator in \sapphire\core\ManifestBuilder.php on line 447

Warning: There are two files both containing the same class: '/googlesitemaps/code/GoogleSitemapDecorator.php' and ''. This might mean that the wrong code is being used. in \sapphire\core\ManifestBuilder.php on line 449

Would appreciate any help with this? I'd like to avoid a clean install if I can just upgrade...

Posted to: 2.4.0 Beta Upgrade Errors Show Thread | Post Reply

Re: Upgrade from 2.3.x to 2.4.0

drobinson — Fri, 19 Feb 2010 10:05:02 +1300

Thanks, that was all I needed. Nested URLs are working perfectly.

Posted to: Upgrade from 2.3.x to 2.4.0 Show Thread | Post Reply

Re: Upgrade from 2.3.x to 2.4.0

ajshort — Wed, 17 Feb 2010 22:59:50 +1300

Hopefully all you should need to do is add "SiteTree::enable_nested_urls();" to your _config.php file, and visit yoursite.com/dev/tasks/MigrateSiteTreeLinkingTask. If you have custom code relying on unique URLSegment values or using $URLSegment to generate links some things might break.

Posted to: Upgrade from 2.3.x to 2.4.0 Show Thread | Post Reply

Re: Upgrade from 2.3.x to 2.4.0

drobinson — Wed, 17 Feb 2010 18:52:18 +1300

Are there instructions published yet about how to begin using the hierarchical URL/page structure after upgrading to 2.4? All I've seen is a quick mention of it being a mode to choose between flat URLs and hierarchical ones.

Posted to: Upgrade from 2.3.x to 2.4.0 Show Thread | Post Reply

Re: "Server Error" on unpublish and delete since upgrade to 2.3.5

dbenton — Tue, 16 Feb 2010 08:15:12 +1300

Indeed, removing

public function onBeforeDelete(){
parent::onBeforeDelete();
$this->deleteAttachedFiles();
}

from my Page class did the trick.

Posted to: "Server Error" on unpublish and delete since upgrade to 2.3.5 Show Thread | Post Reply

Re: "Server Error" on unpublish and delete since upgrade to 2.3.5

dbenton — Tue, 16 Feb 2010 08:02:15 +1300

Thanks, Willr. I knew there had to be a good way to debug asynchronous requests...

The issue seems to have to do with the removal of the now deprecated HasManyFileManager. Just to document the issue in case someone else has it, I'll post what I learned below. I think the method in question was added as part of the HasManyFileManager documentation and I forgot to remove it when I upgraded and moved to DataObjectManager.

ERROR [User Error]: Uncaught Exception: Object->__call(): the method 'deleteattachedfiles' does not exist on 'Page'
IN POST /admin/EditForm
Line 576 in /path/to/sapphire/core/Object.php

Source
======
567:             case isset($config['function']) :
568:                return $config['function']($this, $arguments);
569:
570:             default :
571:                throw new Exception (
572:                   "Object->__call(): extra method $method is invalid on $this->class:" . var_export($config,
true)
573:                );
574:          }
575:       } else {
* 576:          throw new Exception("Object->__call(): the method '$method' does not exist on '$this->class'");
577:       }
578:    }
579:
580:    //
-----------------------------------------------------------------------------------------------------------------
581:
582:    /**

Posted to: "Server Error" on unpublish and delete since upgrade to 2.3.5 Show Thread | Post Reply

Re: Charging clients for upgrades?

Double-A-Ron — Mon, 15 Feb 2010 15:56:53 +1300

I'm in the same boat as Will. Annual support fee that is completely optional for the client. I just make sure they understand what that fee gives them. If not explained correctly, these fees can sometimes be misconstrued as "hidden".

As a Freelancer, it doesn't really bother me if they go for it or not, but I do try to persuade them to do so as upgrades often have a carry-on effect of reducing support contact. A freelancer's time is better spent elsewhere. It's also a valid reason and very positive way to keep in touch with clients.

If they don't take a support contract, I simply charge for the time at my hourly rate as they request. So the decisions is really a risk and cash-at-hand related one for the client.

It's not alot different to buying a new car. You can buy a service plan, or pay as you go in bigger increments.

Aaron

Posted to: Charging clients for upgrades? Show Thread | Post Reply

Re: Upgrade from 2.3.x to 2.4.0

Ingo — Mon, 15 Feb 2010 08:50:20 +1300

I've updated the UPGRADING file, and commented on the stale manifest ticket

Posted to: Upgrade from 2.3.x to 2.4.0 Show Thread | Post Reply

Re: "Server Error" on unpublish and delete since upgrade to 2.3.5

Willr — Sat, 13 Feb 2010 12:56:59 +1300

if you have firebug installed (Firefox plugin) enable it then view the 'Console' tab and scroll down to the failed request. The response of that request should have the actual error message reported by SilverStripe (if you're not in devmode, enable it as well then try again). You could also look up the server logs - which should report the actual error as well.

Posted to: "Server Error" on unpublish and delete since upgrade to 2.3.5 Show Thread | Post Reply

"Server Error" on unpublish and delete since upgrade to 2.3.5

dbenton — Sat, 13 Feb 2010 12:12:53 +1300

Hello,

I upgraded a site to 2.3.5 a little over a week ago, and since then I cannot delete or unpublish content. When I try, I get the ajax [...] for a few seconds followed by [ (!) Server Error ]. I have no idea how to debug this one. Any suggestions?

Thanks,
David

Posted to: "Server Error" on unpublish and delete since upgrade to 2.3.5 Show Thread | Post Reply

Re: Upgrade from 2.3.3 -> 2.3.6

Sunnybex — Fri, 12 Feb 2010 20:35:27 +1300

well, my problem was the core folder on my Hetzner-Server, public_html. It links to somewhere else, so if it is overwritten or deleted, the content is not touched here. (Maybe it´s the save-mode for idiots like me...) Anyway, never touch the public_html on Hetzner, just replace the folders inside. Nevertheless, you can call them and they will restore the folder with the ss2.3.3 (or whichever) from 'somewhereelse' and you can see the two folders with the old and the newer version.
And then, yes, it is a good way two rename the folders you would like to upload, then upload them in that public_html-file, delete the old ones from the sever and rename the new ones. (dev_build + flush)
Worked fine for my and now it´s time for tea....

Posted to: Upgrade from 2.3.3 -> 2.3.6 Show Thread | Post Reply

Re: Upgrade from 2.3.3 -> 2.3.6

dompie — Fri, 12 Feb 2010 06:59:51 +1300

make sure to (first) delete the old folders and then paste the new folders.

Posted to: Upgrade from 2.3.3 -> 2.3.6 Show Thread | Post Reply

Re: Upgrade from 2.3.3 -> 2.3.6

Sunnybex — Fri, 12 Feb 2010 00:14:12 +1300

Hi,

I got exactly the same problem: after Dompie's steps 1) and 2), and went to admin/dev/build - I still have version 2.3.3 shown in the backend. But the version files in css, saphire and jsparty (on the server) tell me it is SS 2.3.6.

Ok, I skipped the editing and the tea, but it should be the upgraded version anyway, shouldn't it?

Thanks for your help

Bex

Posted to: Upgrade from 2.3.3 -> 2.3.6 Show Thread | Post Reply

Re: Upgrade from 2.3.x to 2.4.0

Dave L — Thu, 11 Feb 2010 12:20:28 +1300

> (since its usually the last thing we do)

Not trying to be confrontational but would say it should be kept up-to-date, if not necessarily detailed and complete, to help downloaders of early releases like myself who end up posting to forums because the info's missing.

Re: my issue - I ended up deleting the cache folder and that resolved my issue and dev/build on 2.4 ran fine As to how people can locate their own cache folder I don't know.

Posted to: Upgrade from 2.3.x to 2.4.0 Show Thread | Post Reply

Re: Upgrade from 2.3.3 -> 2.3.6

dompie — Thu, 11 Feb 2010 10:54:25 +1300

Ay damn...i tricked myself ^.^

I deleted the old files inside my workspace, put the new inside that directory and uploaded them to the server. But i did not delete them on the server -.-'

Posted to: Upgrade from 2.3.3 -> 2.3.6 Show Thread | Post Reply

Re: Upgrade from 2.3.3 -> 2.3.6

Double-A-Ron — Thu, 11 Feb 2010 10:27:23 +1300

The fact that you still see 2.3.3 in the CMS footer really indicates to me that you over-wrote the core directories on top of 2.3.3. That number is pulled from the "version" file inside each directory. So that file hasn't updated, who knows what else.

I've had trouble with this in the past. These days if the update is a manual one like this, I will upload the core directories as a different name (e.g. "sapphire2"). Then delete the originals and rename the new directories. Followed by a Dev build.

Posted to: Upgrade from 2.3.3 -> 2.3.6 Show Thread | Post Reply

Upgrade from 2.3.3 -> 2.3.6

dompie — Thu, 11 Feb 2010 09:10:44 +1300

1) i replaced folders cms, sapphire and jsparty uploaded and run /dev/build?flush=1
Version Number 2.3.3 was still shown in Backend
2) replaced folder themes and root files and run again /dev/build?flush=1
Version Number 2.3.3 was still shown in Backend
3) edited in LeftAndMain.php the static link output and changed it back to original
4) Went for a cup of tea, thinking and then i relogging...suddenly i reveive a website error for the backend, frontend works fine.

5) Done a /admin/?isDev=1
Output:

[User Error] Uncaught Exception: Object->__call(): the method 'gethtmleditorconfigforcms' does not exist on 'Member'
GET /admin/?isDev=1

Line 551 in htdocs/sapphire/core/Object.php
Source

542             case isset($config['function']) :
543                return $config['function']($this, $arguments);
544
545             default :
546                throw new Exception (
547                   "Object->__call(): extra method $method is invalid on $this->class:" . var_export($config, true)
548                );
549          }
550       } else {
551          throw new Exception("Object->__call(): the method '$method' does not exist on '$this->class'");
552       }
553    }
554
555    // -----------------------------------------------------------------------------------------------------------------
556
557    /**

Trace

* Object->__call(getHtmlEditorConfigForCMS,Array)
* Member->getHtmlEditorConfigForCMS()
Line 158 of LeftAndMain.php
* LeftAndMain->init()
Line 84 of CMSMain.php
* CMSMain->init()
Line 113 of Controller.php
* Controller->handleRequest(HTTPRequest)
Line 277 of Director.php
* Director::handleRequest(HTTPRequest,Session)
Line 121 of Director.php
* Director::direct(/admin/)
Line 118 of main.php

Any ideas how i can fix this?

Posted to: Upgrade from 2.3.3 -> 2.3.6 Show Thread | Post Reply

Re: Upgrade from 2.3.x to 2.4.0

Willr — Thu, 11 Feb 2010 08:56:12 +1300

Will, it'd be nice if the upgrading file and the above page had more explicit instructions as you mention - i.e. copy/remove x folders. The upgrading file with the 2.4 download is out of date.

Can you make a ticket for updating the UPGRADING file on open.silverstripe.org and any issues you have with in. Will be a good reminder to update it (since its usually the last thing we do)

Posted to: Upgrade from 2.3.x to 2.4.0 Show Thread | Post Reply