Anonymous | Login | Signup for a new account | 2023-09-30 07:51 CDT | ![]() |
Main | My View | View Issues | Change Log | Roadmap | Docs | Wiki | Repositories |
Relationship Graph | [ View Issue ] [ Dependency Graph ] | |||
|
||||
|
Viewing Issue Simple Details | |||||
ID | Category | Type | Reproducibility | Date Submitted | Last Update |
0000620 | [In-Portal CMS] Admin Interfaces | feature request | N/A | 2010-03-15 13:03 | 2010-03-15 13:04 |
Reporter | alex | View Status | public | ||
Assigned To | |||||
Priority | normal | Resolution | open | ||
Status | active | ||||
Summary | 0000620: Export language packs to other site | ||||
Description |
Currently we have functionality, that allows us to export language pack(-s) to file and then import that file to another site. I propose we add functionality, that will allow us to export+import language pack directly to other site without temporary file being created. For this to work we need to add 3 more field to export form: * target website name (should also have In-Portal installed); * administrator's username; * administrator's password; * overwrite existing checkbox. When entered system will try to login to target site using data provided and remotely import language pack using specified option(-s). For even more security we could limit user's who can perform such type of import (e.g. new language permission: advanced:remote_import) and even limit IP/IP range from what such type of import could be performed. If we look a little bit deeper into this we could create SOAP/XMLRPC server, to handle any type of remote interactions with in-portal installation. |
||||
Additional Information | Do via XML at first. Later will convert to SOAP. |
Main | My View | View Issues | Change Log | Roadmap | Docs | Wiki | Repositories |
Web Development by Intechnic![]() In-Portal Open Source CMS |