Hello there,
I'm always getting an update notice in the backend for AJAX Toggler, but the version proposed is 3.2.1 only for J! 3, and i'm still on 2.5 (specific version i guess). Is it a normal behavior ?
1. Yes, each slave can use own database tables for certain extension and hence have own unique data managed from site's own backend. 2. It's impossible, there are 2 options: a) each site uses own database tables and hence have own independent content managed from own backend. b) all ...
... this, you had mentioned: Yes, you can register, delete users, save profiles, block/activate/deactivate users in either Joomla or phpBB frontend or backend. Another user will be also changed. I am wondering, how is this bridge able to do that without editing the core files? They cant do that with ...
... this, you had mentioned: Yes, you can register, delete users, save profiles, block/activate/deactivate users in either Joomla or phpBB frontend or backend. Another user will be also changed. I am wondering, how is this bridge able to do that without editing the core files? They cant do that with ...
... major. In 1.2.3 update, a lot changed in how things are done. Nice thing is, the last update seems to be the final bits that were changed in the backend that could cause some issues with developing 3rd party apps. My wish list is for the time that p8pBB3 Bridge catches up with EasySocial and ...
... ⋅ Fix: table ordering in frontend. ⋅ Feature: new settings 'Show Limit Box', 'Show Ordering Options' and 'Print Layout' for Backend View in component settings and report settings. ⋅ Feature: {VALUE} tag for 'Footer Label' field (ex 'Footer Custom Value'). It allows ...
... create new articles and games scores and I need it to have a mobile template that the admin can choose (again from front end - or an intermediate backend - i.e. not the full joomla backend) what they want to show on the mobile version - from a list that I would make available. (it will be for ...
... child admins via Joomla permissions. So actually child site admin should not be assigned to Super Users but to a custom group which can login to backend but has limited permissions. I think that steps below have same logic. So actually each subsite will have a special usergroup with certain permissions ...