A solid accreditation process helps educational institutions meet the top standards they establish. Creating a digital one in Salesforce for higher education can be complicated if a school needs a custom process to sync data seamlessly with other workflows already in place. 

In this common scenario, an educational institution would have to seek custom Salesforce development or find a trusted third-party tool on the AppExchange marketplace. You can save research time by going straight to Titan. 

They provide software solutions for Salesforce and higher education organizations. For example, Titan recently helped a college build an accreditation process portal using no code! 

The college originally had a PDF document for collecting information, which then needed to be manually entered into Salesforce. It was an extremely labor-intensive process for the college before turning to TITAN for help. 

Here is a high-level list of tasks in Salesforce the higher ed college accomplished with its new fully automated accreditation process:    

• The college has a portal to guide users through an easy accreditation process.
• The accreditation portal has a secure login for users with 2-factor authorization.   
• Salesforce data is automatically pre-filled into forms to minimize manual inputs.
• Any submitted data from the portal is transferred to Salesforce CRM for the higher education college.
• Users can preview and upload files to the accreditation portal, which are sent to Salesforce instantly.
• Users can quickly fill out forms with interactive radio buttons that collect information for Salesforce.
• The accreditation portal shows users the progress of an application using tick icons. This experience lets users log out of the portal and complete the application at a more convenient time. 
• The accreditation portal can collect information that creates multiple Salesforce records, such as a few location details. 
• Users can pay for their application through the accreditation portal. 
• Users can download a PDF version of all the information they provided to the accreditation portal.
• The whole accreditation process can be tracked in Salesforce every step of the way. 

To see the accreditation portal in action, check out this video: 

See you on the next one!

This is the most comprehensive list of best Salesforce Developer blogs on the internet and I’m honored to have become part of this elite list!  Feedspot expert review team has done a lot of research, reviews, analysis to rank these blogs.

These blogs are ranked based on the following criteria:

• Google reputation and Google search ranking
• Influence and popularity on Facebook, Twitter, and other social media sites
• Quality and consistency of posts.
• Feedspot’s editorial team and expert review

You can have a look at the full list by clicking here.

✓ What is 403 Forbidden Error

The 403 Forbidden Error is an HTTP status code that is sent back by the server when the client (user) who initiated the request doesn’t have permission to access a specific page or resource.

✓ Causes of 403 Forbidden Error

There are many scenarios that can trigger 403 Forbidden Error in WordPress. The following are the common causes:

• Corrupt .htaccess file
• File permission issues
• Incompatible or faulty plugins

✓ Solution

WPBeginner has written an in-depth article on fixing the 403 Forbidden Error in WordPress that will help you to fix the corrupt .htaccess file, repair folder and file permissions, and finding out the incompatible or faulty plugins. If you’ve tried everything described in that article and you still facing 403 Forbidden Error, then it’s the time now to look into ModSecurity configuration.Fix 403 Forbidden Error in WordPress caused by ModSecurityCLICK TO TWEET

What is ModSecurity (mod_security)

ModSecurity is an open-source firewall application (or WAF) supported by different web servers such as Apache, Nginx and IIS, and protects web applications such as WordPress from various code injection attacks. It uses regular expressions and rule sets to block commonly known code injections.

WordPress 403 Forbidden Error and ModSecurity (mod_security)

ModSecurity might give you false-positive results when you work with WordPress posts and comments. When you post (save or update) any data to admin-ajax.php, page.php, post.php (and bb-post.php if you’ve BBPress active) pages, ModSecurity sometimes consider it (of course, falsely) as code injection and respond with 403 Forbidden Error. To fix this, you can either add specific rules for WordPress exclusion into ModSecurity config or disable ModSecurity completely.

• Add specific rules for WordPress exclusion under ModSecurity (mod_security)

Follow the steps given below to whitelist WordPress under ModSecurity.

Find whitelist.conf or exclude.conf file under /usr/local/apache/conf/modsec2/ (CentOS in my case, your’s path can be different)

Add the following Rules:

<locationmatch "/wp-admin/admin-ajax.php">
SecRuleRemoveById 300013
SecRuleRemoveById 300015
SecRuleRemoveById 300016
SecRuleRemoveById 300017
SecRuleRemoveById 949110
SecRuleRemoveById 980130
</locationmatch>

<locationmatch "/wp-admin/page.php">
SecRuleRemoveById 300013
SecRuleRemoveById 300015
SecRuleRemoveById 300016
SecRuleRemoveById 300017
SecRuleRemoveById 949110
SecRuleRemoveById 980130
</locationmatch>

<locationmatch "/wp-admin/post.php">
SecRuleRemoveById 300013
SecRuleRemoveById 300015
SecRuleRemoveById 300016
SecRuleRemoveById 300017
SecRuleRemoveById 949110
SecRuleRemoveById 980130
</locationmatch>

Add the following rules only if you’ve BBPress installed and active

<locationmatch "/bb-post.php">
SecRuleRemoveById 300013
SecRuleRemoveById 300015
SecRuleRemoveById 300016
SecRuleRemoveById 300017
</locationmatch>

You’re done!

• Disable ModSecurity (mod_security) completely if the above WordPress exclusions doesn’t work

You can disable ModSecurity completely by accessing your web hosting Control Panel (different for each control panel) if you’ve VPS or Dedicated Server. Alternatively, you can ask your web hosting provider to disable it completely for you.

* Don’t forget restart your web server after making changes in ModSecurity configuration or after disabling it.

That’s it! You shouldn’t see 403 Forbidden Error anymore now.

Source : https://dipakgajjar.com/fix-403-forbidden-error-in-wordpress-modsecurity/