Vanilla 1 is no longer supported or maintained. If you need a copy, you can get it here.
HackerOne users: Testing against this community violates our program's Terms of Service and will result in your bounty being denied.
User Wall
User Wall
0
This discussion has been closed.
Comments
u will have to fix flickr stream
require_once(dirname(__FILE__) . '/PageListFixed.php');
It's the same when i switch to Vanilla's default theme. I've tried to correct the code, but failed.
Could anyone please help me?
Anyway, i just tried it and decided to play around with the code
-> Lipa: might be old now, but i believed i have solved your problem, it was a css issue.
-> mbrink: about user turning off their wall, this is what i'm trying to achieve atm, however ran into some trouble.
->vaz: i think i might be able to fix the linking when using mod_rewrite, i'll have a look, in the meantime just set the amount of maximum post to something respectable for yourself.
So the order of my priority currently is:
p.s. just another long post :bigsmile:
But thanks for your interest!
So what do i do now in regards to sharing the files? do i upload as my own extension or what?
Okay so i've figured out that with regards to friendly-urls, it's nothing to do with this extension. i've reported this to the author of friendly-url and hopefully a new release will happen.
However if you are confident to edit a .Htaccess file. here is what you need to add.
RewriteRule ^account/([0-9]+)/([0-9]+)$ account.php?u=$1&page=$2 [QSA,L] RewriteRule ^account/([0-9]+)/([0-9]+)/$ account.php?u=$1&page=$2 [QSA,L]
And here my package of User Wall. I've changed the version to User Wall 1.0 Beta 10 (2008-04-30), i've removed a the pagelistfixed and simplifieddiscussion files, as far as i have checked they are not needed.
Download: User Wall 1.0 Beta 10 (2008-04-30)
Extension will upgrade automatically, however users who were using User Wall 1.0 Beta 6, please perform a clean install as mentioned in the readme.txt.
Please post back in this discussion on how i did and any recommendation for improvement, especially in the code.
Thanks and have fun.
Beta 10
- Added: Minor private message system, only wall owner and writer can view the message
- Fixed: PHP4 Friendly (should be anyway couldn't detect any other errors when tested)
- Changed: Made UserWall.css stylesheet more rigid and less compromising
- Changed: Removed pagedlistfixed.php and simplifieddiscussions.css
- Changed: Added another column to the table, extension will upgrade and add column automatically, shouldn't interfere with existing data, but backup anyway
- Minor: Cleaned up some internal codes
- Added: Minor debug function, displays actual errors for certain error traps
I forgot to mention the features added in Beta 9- User wall public comment toggle via account preference, owner can still write independent of account pref *
- Wall comment editing. **
- Fixed: validation for deleting comments **
- Fixed: table creation
- Fixed: table prefix used for table creation, dependant on vanilla config, allows for easy cross custom vanilla install
- Modified: error trapping during extension installation
- Modified: Display IP of commenter based on vanilla role permission, no need for iphistory extension
- Modified/Fixed: Various other small stuff.
- Added: Shows user icon in post.
- Added: Master wall moderator role added (can delete/edit all walls).
- Fixed: Disabled wall feature for applicants
* Still based on role permissions.** Owner of page can only delete, unless they own the post or is a master wall moderator (role).
I think that's about it.
Ultimately the wall funnily as i modified has two levels of permission. There is a role based permission, and there is a personal wall permission. But ultimately writing on the wall still depends on the forum admin allowing the group to write.
So here are 2 examples.
#1, account1 has a role based permission to write, but account2 doesn't allow public to write on his wall. Therefore account1 can't write on account2.
#2, now account3 doesn't have a role based permission to write, but however allows the public to write on his wall, therefore account1 is able to write on account3's wall. account3 won't be able to write on his own wall either because he doesn't have the role permissions to write.
However for editing and deleting the comments, it is based on ownership of the wall and ownership of the comment itself.