FAQ:* How to use permalink provided by WordPress* Some hosting impose strict restriction on mod_rewrite related settings and you are unfortunately unable to use mod_rewrite and original link mode is the only option for you: http:/ /myblog.com/modules/wordpress/?p=123
* Complete mod_rewrite is not available with some hosting or .htaccess is disabled, in this case you can only use the pseudo-permalink setting in Custom: http:/ /myblog.com/modules/wordpress/index.php/123
* Even if you are lucky enough to be able to use complete mod_rewrite, make sure to make .htaccess read only once the file is modified, or write the file manually
* The last point: if you are likely to switch from one hosting to another frequently, I would suggest to use the original permalink mode (http:/ /myblog.com/modules/wordpress/?p=123) considering you might lose the chance to use same mode for permalink by which you could lose all your google-indexed page links, even your PageRank!
* How to convert standalone WordPress to XPress or rollback XPress to standalone WordPress?* XPress uses the same tables as WordPress, it is very straightforward to switch between standalone WordPress and XPress. The only thing to be careful is table names, make sure to be compliant with XOOPS table prefix.
* Even if you stay with XPress, you have the choice to use XOOPS classical layout or WordPress layout: set proper preference in module preferences
* How to make XPress compatible with XOOPS 2.0*, 2.2* and 2.30?* Upload the folder /Frameworks/ onto your server under your XOOPS ROOT folder. If you are using XOOPS 2.2*, make sure to remove the folder of /Frameworks/xoops22/
* How is the relationship between XOOPS user table and WordPress user table* XPress uses XOOPS user table as the working table and WordPress user table as a mirror, in other words, only create a backup account in WordPress when a user submits his first WordPress post
* Sometimes a new user is refused submitting blog with the message of “you don’t have the permission”. In this case, make sure you have set group permissions for the module properly, and clean up the cache/wordpress folder where WordPress stores cached data.