Its good idea to create a separate group and place the people whom you want to disable the move button. Assign the required permissions to this group except delete. Then these people won't be able to see the Move button.If you modify the OOTB code then it will affect on all users.

It depends in the stat file level. Dispatcher does not automatically invalidates the child pages even the replicated/parent page has iparsys.

You can use the Sling API as Scott mentioned.

Hi Rohit,I was able to make it work. It was a apache config change. There was a small syntax change between Apache 2.2 and 2.4 causing this issue. This is fixed now.Thanks for your willingness to help.Thanks.

Hi,It suppose to get this on publish instance. But this is not working on publish. If it works on publish then it will work o  dispatcher as well.Thanks.

Thanks. It worked. The dispatcher documentation is little confused. I found below article is helpful.http://aempodcast.com/2016/infrastucture/year-desert-aem-dispatcher/#.Wc7U7VtSxaQ

Hi,I have already added all these as mentioned in the article.Thanks.

True.But dispatcher is not forwarding the requests to AEM instance for child pages.This is what I am trying to explain. Sorry for any confusion.

I understand.  Whenever I request for these sub-level pages then those are serving from the dispatcher cache (Time stamp of those files are not changing). It suppose to fetch those from publish and replace these invalidated cached files.So its clearly not invalidating the sub folders.

Thanks for the explanation.If you invalidate the /content/myproject/en/firstlevel/secondlevel/thirdlevel/something.html, it is touching all the .stat files. However, its not invalidating the files in this folder/subfolders.Please let me know if you need more details.