Skip to main content

Hello World!

I’ve been itching to get this going for some time now, and decided to simply take the plunge!  I’ll be initially importing my previous posts from the Arke Systems Blog and then should have some more new tidbits shortly after.

I am somewhat new to the blogging world (and newly certified with Sitecore) and my hope is that this can eventually become a handy resource for others getting started with our favorite CMS! Initially there was a lot of struggle for me to find out basic information on how to do seemingly simple things (training really is the best way to go), so I’ll be posting a lot of small tips as I go along, and if I gloss over anything – comment!

One thing I'm really hoping for from this blog is some feedback – so please, comment and let me know where things can be improved or if this was useful at all – or if you’d like me to post about a particular topic.

Looking forward to the future!

Comments

  1. Hi Amy! Welcome to Sitecore blogging community!

    ReplyDelete
  2. This comment has been removed by a blog administrator.

    ReplyDelete
  3. The slim enchantment leaves a long-lasting impression 파라오카지노 when enjoying in} at the on line casino. And second, they make it simpler for players to turn out to be acquainted with new video games and casinos after they begin enjoying in} on-line. It is a benefit or an inducement to boost a player's involvement with an online on line casino.

    ReplyDelete

Post a Comment

Popular posts from this blog

Using the Source Property

For each of the properties in your template you can set a source for it, this isn’t always used but can improve user experience drastically when done throughout a site. The source field comes in to play whenever you are using any of the following fields: Droplink, Droplist, Droptree, File, Grouped Droplink, Grouped Droplist, Image, Multilist, Treelist, Rich text field and a number of others. There are various ways of setting these up to achieve different results – but in general you are using the source to limit the set of items that can be used, and this requirement can also help you determine what kind of field to use. For example, if you have a Set of items all split down into sub folders and want the content editor to make use of the tree, you could use a TreeList or Drop Tree, but if you just want a set of items without the opportunity to see where those items are – multilists or droplinks are the way to go. For Images you’re generally just specifying where to look for and put th

Web Forms for Marketers: Send Email

To have the save action for your form actually send email, you will need to change one of the settings, otherwise you will receive this error whenever submitting the form: We experience a technical difficulty while processing your request. Your data may not have been correctly saved. Also in your log (/data/logs/newest log file) you will see this error after the form has been submitted: Exception: System.Net.WebException Message: The remote name could not be resolved: 'example.host' Source: System at System.Net.ServicePoint.GetConnection(PooledStream PooledStream, Object owner, Boolean async, IPAddress& address, Socket& abortSocket, Socket& abortSocket6, Int32 timeout) at System.Net.PooledStream.Activate(Object owningObject, Boolean async, Int32 timeout, GeneralAsyncDelegate asyncCallback) at System.Net.PooledStream.Activate(Object owningObject, GeneralAsyncDelegate asyncCallback) at System.Net.ConnectionPool.GetConnection(Object owningObject, GeneralA

Determining Page Editor Status with Javascript

     Often you’ll need to know if you are inside or outside the Experience/Page Editor in order perform an action. If you are on the server-side in code-behind you can check the Sitecore.Context.PageMode to determine which mode you are in. But what about at runtime? Javascript per usual can save the day! Though you can find PageModes through the Sitecore object if it is available to the browser, it may not be there. Depending on how things have been set up with your solution, the Sitecore object may not return a null as would be expected when checking to see if you can access it. Instead Sitecore may be undefined.  Contrary to some examples on the web with only null checks, this quick little change in your script can correctly let you know if you are in the page editor: Just take a look to see if isPageEditor is true or false and you’re set!