Update Cache Archiv
With this MM3-Utility you can update the pages of a cache archive. The links to pages already archived are followed up by one or several start pages. Changed pages are stored in an update archive.
Start of MM3-Utility
You start the update with one of the following script files in the folder: MM3-WebAssistantProfessional/script/
With Next you get the configuration dialog: MM3-Update You can save a updateing configuration in a Set. At first use the set default. With New you create a new set. Furthermore you can Rename or Delete a set with a pop-up menu.
The links to pages already archived are followed up by one or several start pages. Changed pages are stored in an update archive. Enter the URL for every start page in a new line.
There are restrictions at the link following of dynamic elements like Java-Skript and Flash.
The parameters of the Surf Set are used with the exception of Marker and Prefetch. Only that cache archive is updated which have the write access in the select surf set. The pages are updated by following of links in the cache archive. If the surf set only consists of one archive, then the links which are marked green are followed up (see Surf Set/Marker).
The updated pages and their new resources will be archived in this archive. The name of the update archive corresponds to the name of the cache archive to be updated with a name addition. The todays' date is per default used as an addition, this is indicated by a character pattern. The character pattern starts with the opening bracket [ and ends with a closening bracket ].
You can check the number of pages to be updated before the storage. To this you deactivate the update archive. With this result you can determine additional necessary start pages or you can indicate restrictions for the link following.
Pages only are archived if the update archive is activated.
The Utility MM3-Update updates all files which are older than the adjusted time of reuse.
You can set the reuse as relative or absolute time.
If you don't set the date completely, the todays' date and the time of day is used.
Some servers break off downloading files automatically. The files are requested in much faster consequence as this is carried out at the surfing. You therefore insert a waiting time, at which you let best vary these between a minimal and maximum waiting time.
All links followed up are logged per default.You are able to log the following URLs in addition:
In the summary you can log links not followed in addition.
Pages and resource occurring repeatedly are logged only once.
If too many pages are downloaded at a mirroring, you can prevent this with a filter so. You can define in a filter: domain, directory, file name, file or MIME types. With the additional parameter Follow the effect of the filter is controlled by the link following.
If both, Follow and Exclude, meet a link, then the link will be excluded and the page won't be downloaded.
The detailed structure of the filter is described: Filter for Following Links
Only pages are downloaded from the domain Proxy-Offline-Browser.com, however no pdf documents and pages from the folder /private/ and its subdirectories.
Please select, whether the link has to be followed, excluded or enquired generally.
With Generate filters you can generate the required filters from your start pages (URLs). An additional pattern still can specify the filters or you can manually or with interaction postprocess the filters.
All locally available pages which are excluded by the filter are logged. You hereby can check the setting of the filter.
Cookies can be accepted or blocked depending on filter setting. This supports the protection of data privacy. You also can prevent the representation of history (breadcrumb trail) on a HTML page with that, however.
If both, Accept and Bock, meet a cookie, then the cookie will be blocked.
The detailed structure of the filter is described: Filter for Cookie
All Cookies are blocked.
All accepted cookies are logged. You hereby can check the setting of the filter.
For a password protected web site the user name and the password can be saved.
You can in addition indicate whether the password shall be saved at the call of a protected page.
Passwords can be protected with a master password. The master password has to be entered at every start of the Utility MM3-Update.
Only log-ins can be processed if the log-in is requested over the http protocol header (registration with dialog box of the browser). Log-ins over a HTML-form aren't supported.
Start of the update
After you have filled out the required configuration or selected a set you start the update with Start Update. In a dialog the updating is logged. A summary is displayed at the end of the updateing or at the cancel. A report can be displayed in the browser.
Display of the reports update archive
You reach the reports on the local sitemap (or direct by URL: http://127.0.0.1:8080/update/). You select the desired report from a list. A report includes all changed pages of an update. Passages joined newly in a page are displayed. You can configure the display as follows:
You can surf in a report. At the surfing the changes are shown to you. (Per default blue highlighted). At the online surfing all pages are stored in the update archives (not in the cache archiv).You recognize this mode at the update symbol instead of the surf set symbol . If you click on the update symbol , then the update mode is finished. You reach the update mode at the call of a report. The called report determines the update archive and the surf set. If several reports are displayed at the same time, the report loaded last determines the update archive and the surf set. The used surf set is displayed at the main menu and the tool tip indicates the update archive.
With a click on the symbol for the synchronization all resources are copied into the corresponding cache archive. The copied domains are logged. After this you can delete the report and the update archive.
Mirror Convert or join of cache archives |
© MM3Tools, 7 November 2016 WebAssistant@MM3Tools.comLegal information