Ok, just wanted to give an update. I’ve made some headway on this and am updating this for others who may end up in a similar situation. This is still in development, and I will add more detail later as I get closer to finishing. I’m getting assistance from one of my favorite developers on this. Seems I am close, but this stuff is tough for me. Since the post included 403 error, I guess I should give the short fix here: My subdomain root folder was not loading anything because it was not loading files from the websites root files. theres nothing at public_html/garyatwell.example.com, so make it point to public_html/ instead
First of all, I need to create a new context and name it after the employee.
I need to go into the cpanel (if using godaddy, yourwebsite.com/cpanel) and create a subdomain, and make sure the root folder is not a new root folder like it will likely want to do. Example: garyatwell.example.com will have a root folder of public_html/garyatwell.example.com, change it remove everything after public_html)
Go to your domain manager and make sure to create a new A record under the DNS and make sure that it points to the website IP (open command prompt, type in ‘ping yourwebsite.com’)
She has created user contexts and groups so that way adding/removing people and permissions will be a snap. Also, since we created that context earlier, users will be able to log in at garyatwell.example.com/manager and only be able to see their own files, stay out of the website root files, and be able to handle their own back end. Make sure your security settings are good and be sure to dogfood yourself on this so you can make sure you didn’t overlook anything and leave your site vulnerable.
Another issue I had was setting up MIGX properly. Below are my personal notes I created and they should be easy to follow.
You’ll need to go to Elements and create a new Template Variable. Always name them with MIGX- in front. Add in a caption that tells the user what type of migx this is (call to action, for example.)Then, click on Input options, and from there, past the code below in the appropriate box. Do not make it static. Choose input type migx
Form tabs code - this one is what you see in the back end of modx and is when you’re actually creating things you’ll be calling later. This is for the pop up window in the back end.
[{“caption”:“Call to Action”, “fields”: [
{“field”:“ctaTitle”,“caption”:“Title”},
{“field”:“ctaDesc”,“caption”:“Description”,“inputTVtype”:“textarea”},
{“field”:“ctaButton”,“caption”:“Button Text”},
*{“field”:“ctaLink”,“caption”:“URL”} *
]
}]
to use these, use [[+ctaTitle]] in the [[getImagesList?]] below
Grid Columns - goes into the back end and is what you see in the back end of modx when you are entering content on the page. You’re kind of building the back end menu this way. This is for the back end where you are on the page and its showing you things at a glance.
[{“header”: “Title”, “height”: “50”, “sortable”: “true”, “dataIndex”: “ctaTitle”},
{“header”: “Description”, “height”: “50”, “sortable”: “true”, “dataIndex”: “ctaDesc”},
{“header”: “Button Text”, “height”: “50”, “sortable”: “true”, “dataIndex”: “ctaButton”},
{“header”: “URL”, “height”: “50”, “sortable”: “true”, “dataIndex”: “ctaLink”}
]
below is code that shows how to change the tv type to allow images. Note the “inputTVtype”:
{“field”:“employee-image”,“caption”:“Image”,“inputTVtype”:“image”} -
on the MIGX under the Input Options tab, the top one goes in “Form Tabs” and the bottom one goes in “Grid Columns”
set it to show on your Home template and voila, you have a migx table for the CTAs
on the MIGX TV *
thgen go to template access, give access to the template you want to apply this to, then name things in General information tab
Adjust this code to match the things you have named.
This goes in the template
[[getImageList?
&tvname=insert tv name you saved as above - MIGX-***
&tpl=@CODE:<li>[[+idx]]<h1>[[+title]]</h1><p>[[+ctaDesc]]</p></li> ]]