alenpelin/fridaycore

FridayCore is a set of Sitecore extensions that every Sitecore site needs.

fridaycore's Issues

Create NuGet packages

Create a bunch of NuGet packages:

• FridayCore
  • FridayCore.Configs (App_Config only)
  • FridayCore.Binaries (assemblies only)
• FridayCore.Source
  • FridayCore.Source.Configs
  • FridayCore.Source.Code

When creating an account don't email the password

I think it would be better practice (and probably more secure) to send a link with userid and expiration date via jwt and force the user to choose their own password

https://jwt.io/

This would mean

• admin passwords are floating around in emails
• the user only had a limited time to action the email

[AccountResetRules] Do not reset password

Add an option not to reset or change password so only to unlock account if it is locked.

Sync items

Create an extension that lets developer link several items and choose item name and/or specific fields to be synchronized across linked item chain. It is like item cloning but simpler and can be used in development only.

Add configuration node to write message to log during initialization

<processor ... log:warn="This processor is only for troubleshooting, remove ASAP" />

Configuration engine to access connection strings

Extend configuration engine to use and :

<configuration>
<sitecore>
  <settings>
    <setting name="MailServer" value="$(connectionstring:smtp/DataSource)" />
    <setting name="MailServerUserName" value="$(connectionstring:smtp/UserName)" />
    <setting name="MailServerPassword" value="$(connectionstring:smtp/Password)" />
    <setting name="MailServerPort" value="$(connectionstring:smtp/Port)" />
  </settings>
</sitecore>
</configuration>

where ConnectionStrings.config file is following:

<?xml version="1.0" encoding="utf-8"?>
<connectionStrings>
...
  <add name="smtp" connectionString="Data Source=localhost,25; User ID=smtpusername; Password=smtppassword" />
...
</connectionStrings>

[SignUpRules] Hide code if none of sign up rules has it

Hide code textbox from the signup page if none of sign up rules has it set up.

[Content Editor] Package item context menu option

In Content Editor, add "Package this item" menu option when right-clicking an item in the content tree. When selected, the dialog is poped-up which asks whether to include descendants or not. When confirmed, the package is created and downloaded to the browser.

Support Identity Server

Add the ability to perform account creation via the Identity Server login

Respect media extension in URL

When having several same-name media items with different extensions, the request extension must be taken into account when picking one of them prior to apply sort order.

Scenario:

1. Upload two different images with image.png and image.jpg names to Sitecore
2. Request /-/media/image.png and /-/media/image.jpg

Actual Result:
Both images are the same

Expected Result:
The images are different and corresponding

Automatically install Sitecore packages from special folder

When configured, automatically install all packages located in specially configured folder, proposed location is /App_Data/AutoPackages.

[ErrorPageDelivery] Prevent re-generating file too often

Search engine indexing status for page

Feature: SearchEngineStatus

Support of secret phrase in sign up rule

Feature: SignUpRules

Add support of adding optional "secret" phrase to sign up rules so users having identical email domain could get different roles like [email protected] with "ninja" secret gets admin account and [email protected] with "summer" secret gets only author one.

[SXA] Static error page generation on CD

OOB SXA 1.7 generates static error page on CM instance when special Ribbon button is pressed. We need to fix it to be fully automatic - so the page is generated on all instances on item:save(:remote) event.

Implement custom 'app:init:completed' event

Implement custom app:init:completed event that is raised when application finished initialization and first request has successfully served.

Reset to specified password in AccountResetRules

It should be possible to hard-code password in configuration file to reset account password to. The use case is for local development with specific conventions regarding user accounts and passwords.

[AccountResetRules] Only reset account if default

Only reset account if it is default (admin:b)

Cascade update insert options of inherited templates

Feature: InsertOptionsCascade

Consider 3 templates:

• T1
• T2 inherits T1
• T3 inherits T2 (and T1)

In Standard Values of each of them update Insert Options so you can insert items of same type and all derived ones:

• T1 insert options for T1
• T2 insert options for T1 and T2
• T3 insert options for T1, T2 and T3

Update insert options of T1 so that insert options also include Folder template.

Actual Result:
This does not affect T2 and T3 - they still don't have Folder template in insert options.

Expected Result:
All T1, T2 and T3 have Folder template in insert options

Send new password to email when resetting user account

Feature: ResetUserAccount v2

Improvement: add an ability to send new password to a number of pre-defined emails

EmbeddedResource configuration files

Feature: EmbeddedResourceConfiguration