Answered Modx Auto post to Social sites

Mayanktaker, you should probably start a new topic for the import question, since it's unrelated to this topic.

On the automation -- when a document is published, MODX fires the OnDocPublished event. A plugin connected to that event will have access to the resource and could auto publish it anywhere. I'm fairly certain that that event fires when you publish an Article, so it's the natural way to do it.

The difficult part would be providing a way for the user to manage which services were used and record the necessary user information (keys, secrets, tokens, etc.) for each service, and providing templates for the text to be sent to each service and letting the user manage them.

After writing Notify, I can tell you that the truly horrible part is testing everything as you go. I'd expect that part alone to take many, many hours.

@Mayanktaker Thanks for trying Quill. I'm glad you liked it. Moving your articles from Articles to Collections is very easy. You just need PHPMyAdmin. This is a repeat of a solution I posted some time ago:

Using phpMyAdmin, update the following columns using SQL queries (SQL tab):

1). For the container resource:

Change the class_key column : from 'Article' => 'CollectionContainer'

UPDATE `modx_site_content` SET `class_key` = replace(class_key, 'Article', 'CollectionContainer') WHERE id=<your_blog_container_id>;

2). For child resources (Blog posts:)

Change the class_key column: from 'Article' => 'modDocument'

UPDATE `modx_site_content` SET `class_key` = replace(class_key, 'Article', 'modDocument') WHERE parent=<your_blog_container_id>;

3) OPTIONAL: Empty the properties column: (This is just to keep things clean)

UPDATE `modx_site_content` SET properties='' WHERE parent=<your_blog_container_id>;

</your_blog_container_id></your_blog_container_id></your_blog_container_id>

@Mayanktaker Thanks for trying Quill. I'm glad you liked it. Moving your articles from Articles to Collections is very easy. You just need PHPMyAdmin. This is a repeat of a solution I posted some time ago:

Using phpMyAdmin, update the following columns using SQL queries (SQL tab):

1). For the container resource:

Change the class_key column : from 'Article' => 'CollectionContainer'

UPDATE `modx_site_content` SET `class_key` = replace(class_key, 'Article', 'CollectionContainer') WHERE id=<your_blog_container_id>;

2). For child resources (Blog posts:)

Change the class_key column: from 'Article' => 'modDocument'

UPDATE `modx_site_content` SET `class_key` = replace(class_key, 'Article', 'modDocument') WHERE parent=<your_blog_container_id>;

3) OPTIONAL: Empty the properties column: (This is just to keep things clean)

UPDATE `modx_site_content` SET properties='' WHERE parent=<your_blog_container_id>;

</your_blog_container_id></your_blog_container_id></your_blog_container_id>

BTW, unless you like Quill's initial folder structure, you should move Quill's resources to the top level of the site tree and delete the global container (2) since it's only used to separate Quill's resources from any other resources you may have on initial setup.

You have Two options:

OPTION 1: Import your artiiiii (195) blog posts into Quill's Blog container (3)

// Step 1 =>  Change the parent
UPDATE `modx_site_content` SET `parent` = replace(parent,195, 3) WHERE id=195;
// Step 2 => Change the class_key of the imported posts
UPDATE `modx_site_content` SET `class_key` = replace(class_key, 'Article', 'modDocument') WHERE parent=3;
// Step 3 => Clear Cache in the manager

OPTION 2: Change your artiiiiii resource class_key from Article => CollectionContainer

// Step 1: Change the parent's class_key
UPDATE `modx_site_content` SET `class_key` = replace(class_key, 'Article', 'CollectionContainer') WHERE id=195;
// Step 2: Change the posts (child resources) class_key
UPDATE `modx_site_content` SET `class_key` = replace(class_key, 'Article', 'modDocument') WHERE parent=195;
// Step 3 => Clear Cache in the manager

I recommend the first option, because you won't need to update Sytsem Settings anymore.

If you choose the second option, don't forget to update Quill's quill2.blog_container System Setting with the value of your artiiii9 resource, which should be 195. You'd also need to either place your artiiiii resource underneath Quill's folder (2) or move your Quill's resources to the top level of your site tree.

0 rows affected. (Query took 0.0013 sec)