6822
Facebook doesn't show you who blocked you from messages or even from being a friend, because of privacy issues - they don't want to cause any bad blood or retaliation.
I would follow the policies of the more established "social networks" as they probably explored it from the legal perspective.
I would follow the policies of the more established "social networks" as they probably explored it from the legal perspective.
6823
Quote:
in the "themes" subdirectory
Additional themes are at:
http://wiki.lifetype.net/index.php/Templates
Quote:
yes. You make your changes through LifeType interface.
For example, to change your theme:
1) go to:
http://yourwebsite.com/modules/lifetype/admin.php
2) Click on the top menu "Control Center",
3) then on Settings: Block Settings:
4) Select the right "Template" for you
5) click "Updated"
Something else now:
- where can I find Themes for LifeType
in the "themes" subdirectory
Additional themes are at:
http://wiki.lifetype.net/index.php/Templates
Quote:
and is it normal, I have no admin panel for LifeType?
yes. You make your changes through LifeType interface.
For example, to change your theme:
1) go to:
http://yourwebsite.com/modules/lifetype/admin.php
2) Click on the top menu "Control Center",
3) then on Settings: Block Settings:
4) Select the right "Template" for you
5) click "Updated"
6827
Well said, John. I hope, Release 3.0 will address these and many other issues.
We need to work on the "out of box" user experience.
We might have to redesign the kernel, but if we do it right, even with more functionality, it could be more responsive than it is today. Thankfully, there are tons of CMS systems out there, so we can take a look at them to see what they do right and incorporate their Best Practices into XOOPS 3.0
I don't much about the kernel itself (I leave it for the experts), but I'm big on user experience, so I'll be looking after that...
We need to work on the "out of box" user experience.
We might have to redesign the kernel, but if we do it right, even with more functionality, it could be more responsive than it is today. Thankfully, there are tons of CMS systems out there, so we can take a look at them to see what they do right and incorporate their Best Practices into XOOPS 3.0
I don't much about the kernel itself (I leave it for the experts), but I'm big on user experience, so I'll be looking after that...
6828
Quote:
Irmftan, my concern would that XOOPS will become too chaotic, where one part won't work with another, and there will be a lot of compatibility issues, and we'll be spending more time fixing things introduced by an outside module than on improving XOOPS.
I'm with you to keep core light, but I would suggest to include the most important functionality inside the core, so we can ensure that XOOPS works out of the box.
But what are the "Best in class" practices? How is Drupal, Joomla, and some other up and coming CMS systems dealing with it?
And what kind of experience are the users looking for ?
i like to see XOOPS a more and more modular cms. then developers can work on different and details branches and core will be lighter and smaller.
Irmftan, my concern would that XOOPS will become too chaotic, where one part won't work with another, and there will be a lot of compatibility issues, and we'll be spending more time fixing things introduced by an outside module than on improving XOOPS.
I'm with you to keep core light, but I would suggest to include the most important functionality inside the core, so we can ensure that XOOPS works out of the box.
But what are the "Best in class" practices? How is Drupal, Joomla, and some other up and coming CMS systems dealing with it?
And what kind of experience are the users looking for ?
Login
Search
Recent Posts
Who's Online
Donat-O-Meter
| Stats | |
| Goal: | $100.00 |
| Due Date: | May 31 |
| Gross Amount: | $0.00 |
| Net Balance: | $0.00 |
| Left to go: | $100.00 |
 |
|