<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Extension 7: Textfield widths on the “Edit” page</title>
	<atom:link href="http://tobias.baethge.com/2010/03/extension-7-textfield-widths-on-the-edit-page/feed/" rel="self" type="application/rss+xml" />
	<link>http://tobias.baethge.com/2010/03/extension-7-textfield-widths-on-the-edit-page/</link>
	<description>Website of Tobias Bäthge.</description>
	<lastBuildDate>Tue, 05 Apr 2011 01:24:52 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: Lou</title>
		<link>http://tobias.baethge.com/2010/03/extension-7-textfield-widths-on-the-edit-page/comment-page-1/#comment-3231</link>
		<dc:creator>Lou</dc:creator>
		<pubDate>Sat, 21 Aug 2010 12:26:26 +0000</pubDate>
		<guid isPermaLink="false">http://tobias.baethge.com/?p=844#comment-3231</guid>
		<description>I checked at the right time, thank you for the reply, I will take a look at the source code, nice job on that site btw.</description>
		<content:encoded><![CDATA[<p>I checked at the right time, thank you for the reply, I will take a look at the source code, nice job on that site btw.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tobias</title>
		<link>http://tobias.baethge.com/2010/03/extension-7-textfield-widths-on-the-edit-page/comment-page-1/#comment-3230</link>
		<dc:creator>Tobias</dc:creator>
		<pubDate>Sat, 21 Aug 2010 12:20:02 +0000</pubDate>
		<guid isPermaLink="false">http://tobias.baethge.com/?p=844#comment-3230</guid>
		<description>Hi Lou,

thanks for your comment. Unfortunately there is no such documentation on this feature available. It is a custom development I made for that side. It uses AJAX to grab the additional content and then adds it to the table. I can not provide any assistance for this feature, but I can only encourage you to take a look at the source code.

Best wishes,
Tobias</description>
		<content:encoded><![CDATA[<p>Hi Lou,</p>
<p>thanks for your comment. Unfortunately there is no such documentation on this feature available. It is a custom development I made for that side. It uses AJAX to grab the additional content and then adds it to the table. I can not provide any assistance for this feature, but I can only encourage you to take a look at the source code.</p>
<p>Best wishes,<br />
Tobias</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lou</title>
		<link>http://tobias.baethge.com/2010/03/extension-7-textfield-widths-on-the-edit-page/comment-page-1/#comment-3229</link>
		<dc:creator>Lou</dc:creator>
		<pubDate>Sat, 21 Aug 2010 01:06:07 +0000</pubDate>
		<guid isPermaLink="false">http://tobias.baethge.com/?p=844#comment-3229</guid>
		<description>Hello, first this is a wonderful plugin and thanks for it, my question is, on your baseball site when you click a players name, a drop down appears with all that players stats, how did you implement that, is there a step by step documentation to show how it is done? Thanks.</description>
		<content:encoded><![CDATA[<p>Hello, first this is a wonderful plugin and thanks for it, my question is, on your baseball site when you click a players name, a drop down appears with all that players stats, how did you implement that, is there a step by step documentation to show how it is done? Thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: chris</title>
		<link>http://tobias.baethge.com/2010/03/extension-7-textfield-widths-on-the-edit-page/comment-page-1/#comment-3114</link>
		<dc:creator>chris</dc:creator>
		<pubDate>Tue, 03 Aug 2010 17:04:29 +0000</pubDate>
		<guid isPermaLink="false">http://tobias.baethge.com/?p=844#comment-3114</guid>
		<description>No problem and thank you, Tobias. The work you have done is fantastic. I do understand your reluctance to avoid creeping into areas beyond your original objective. Thanks for your help. Regards, Chris</description>
		<content:encoded><![CDATA[<p>No problem and thank you, Tobias. The work you have done is fantastic. I do understand your reluctance to avoid creeping into areas beyond your original objective. Thanks for your help. Regards, Chris</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tobias</title>
		<link>http://tobias.baethge.com/2010/03/extension-7-textfield-widths-on-the-edit-page/comment-page-1/#comment-3112</link>
		<dc:creator>Tobias</dc:creator>
		<pubDate>Mon, 02 Aug 2010 21:30:27 +0000</pubDate>
		<guid isPermaLink="false">http://tobias.baethge.com/?p=844#comment-3112</guid>
		<description>Hi Chris,

no, unfortunately I don&#039;t know how to use S2Member together with my plugin. I have never used or worked with that plugin, so I don&#039;t know the details on how it works. Sorry.

Best wishes,
Tobias</description>
		<content:encoded><![CDATA[<p>Hi Chris,</p>
<p>no, unfortunately I don&#8217;t know how to use S2Member together with my plugin. I have never used or worked with that plugin, so I don&#8217;t know the details on how it works. Sorry.</p>
<p>Best wishes,<br />
Tobias</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: chris</title>
		<link>http://tobias.baethge.com/2010/03/extension-7-textfield-widths-on-the-edit-page/comment-page-1/#comment-3111</link>
		<dc:creator>chris</dc:creator>
		<pubDate>Mon, 02 Aug 2010 18:18:38 +0000</pubDate>
		<guid isPermaLink="false">http://tobias.baethge.com/?p=844#comment-3111</guid>
		<description>Hi again Tobias,
determined not to use this plugin if we can! However to make the last workaround suggested be successful, we need to have the S2Member plugin prevent people without (say) S2member Level 1 or above membership getting to your Table List, Add New table Page. Don&#039;t suppose you (or anyone else here) has figured out a way of that happening have you?

Chris</description>
		<content:encoded><![CDATA[<p>Hi again Tobias,<br />
determined not to use this plugin if we can! However to make the last workaround suggested be successful, we need to have the S2Member plugin prevent people without (say) S2member Level 1 or above membership getting to your Table List, Add New table Page. Don&#8217;t suppose you (or anyone else here) has figured out a way of that happening have you?</p>
<p>Chris</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tobias</title>
		<link>http://tobias.baethge.com/2010/03/extension-7-textfield-widths-on-the-edit-page/comment-page-1/#comment-3110</link>
		<dc:creator>Tobias</dc:creator>
		<pubDate>Mon, 02 Aug 2010 17:27:57 +0000</pubDate>
		<guid isPermaLink="false">http://tobias.baethge.com/?p=844#comment-3110</guid>
		<description>Hi Chris,

thanks for the feedback and information on your current solution.

I understand that you are in need of a more fine-grained control of user actions and rights within the plugin. However, I feel that this is outside the scope of the plugin. See, the goal of the plugin is to offer an easy way to create tables, without the need to manually mess with the HTML code behind it. It takes data, allows easy editing and displays it. However, it is not intended to be a spreadsheet application or graphing tool.

Sure, the features could be extended even further, but there will always be limitations, so it really is hard to fit everyone&#039;s needs. So, while certainly some users (like you) would benefit from such a feature, I&#039;m very sure that most others don&#039;t need it and might only be confused from it. I have experienced this before, and had to see that every new feature, every setting and every option make the plugin harder to use for the people at which it is actually targeted.
Additionally, the implementation would certainly not be easy. There are a few things in the current structure of the plugin that would make per-table user rights very hard to control, and due to that, I don&#039;t want to take that route at the moment. I hope you can understand that.

Best wishes,
Tobias</description>
		<content:encoded><![CDATA[<p>Hi Chris,</p>
<p>thanks for the feedback and information on your current solution.</p>
<p>I understand that you are in need of a more fine-grained control of user actions and rights within the plugin. However, I feel that this is outside the scope of the plugin. See, the goal of the plugin is to offer an easy way to create tables, without the need to manually mess with the HTML code behind it. It takes data, allows easy editing and displays it. However, it is not intended to be a spreadsheet application or graphing tool.</p>
<p>Sure, the features could be extended even further, but there will always be limitations, so it really is hard to fit everyone&#8217;s needs. So, while certainly some users (like you) would benefit from such a feature, I&#8217;m very sure that most others don&#8217;t need it and might only be confused from it. I have experienced this before, and had to see that every new feature, every setting and every option make the plugin harder to use for the people at which it is actually targeted.<br />
Additionally, the implementation would certainly not be easy. There are a few things in the current structure of the plugin that would make per-table user rights very hard to control, and due to that, I don&#8217;t want to take that route at the moment. I hope you can understand that.</p>
<p>Best wishes,<br />
Tobias</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: chris</title>
		<link>http://tobias.baethge.com/2010/03/extension-7-textfield-widths-on-the-edit-page/comment-page-1/#comment-3109</link>
		<dc:creator>chris</dc:creator>
		<pubDate>Mon, 02 Aug 2010 16:44:42 +0000</pubDate>
		<guid isPermaLink="false">http://tobias.baethge.com/?p=844#comment-3109</guid>
		<description>I think we have found a workaround and it&#039;s possibly one you might consider as an update. The trick -we think- is to:

1. embed the users specific table in a page which is password protected. Only the user and (in this application) his boss and mentor have the password to that page.

2. Using something like S2Member move page permssions for list table, add table etc. (i.e. your top level menu) to admin or some permission level out of the reach of each specific table user who wants to edit just their own table (possibly in conjunction with thier boss or mentor). 

3. So now the user gets a private table which can be used to track just about anything about that user (privately) and the user can edit the table in conjunction with anyone else who has access to users private page (here it is his performance and progress). 

4. However user cannot get to the list or the add table etc pages because these pages are protected.

We think this might work, but it would be nice to avoid needing to use S2 just for protecting the list, add etc. pages by (optionally) restricting access to your top level menu items to a specific role. Table Editor maybe?

Now what you have with your table plugin is the core of personalised tables that can be maintained by the person or anyone with access to that persons private page. There are a wealth of applications here. Including ultimately adding personalised visual outputs like graphs maybe?

What do you think, Tobias?

Regards,
Chris</description>
		<content:encoded><![CDATA[<p>I think we have found a workaround and it&#8217;s possibly one you might consider as an update. The trick -we think- is to:</p>
<p>1. embed the users specific table in a page which is password protected. Only the user and (in this application) his boss and mentor have the password to that page.</p>
<p>2. Using something like S2Member move page permssions for list table, add table etc. (i.e. your top level menu) to admin or some permission level out of the reach of each specific table user who wants to edit just their own table (possibly in conjunction with thier boss or mentor). </p>
<p>3. So now the user gets a private table which can be used to track just about anything about that user (privately) and the user can edit the table in conjunction with anyone else who has access to users private page (here it is his performance and progress). </p>
<p>4. However user cannot get to the list or the add table etc pages because these pages are protected.</p>
<p>We think this might work, but it would be nice to avoid needing to use S2 just for protecting the list, add etc. pages by (optionally) restricting access to your top level menu items to a specific role. Table Editor maybe?</p>
<p>Now what you have with your table plugin is the core of personalised tables that can be maintained by the person or anyone with access to that persons private page. There are a wealth of applications here. Including ultimately adding personalised visual outputs like graphs maybe?</p>
<p>What do you think, Tobias?</p>
<p>Regards,<br />
Chris</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tobias</title>
		<link>http://tobias.baethge.com/2010/03/extension-7-textfield-widths-on-the-edit-page/comment-page-1/#comment-3108</link>
		<dc:creator>Tobias</dc:creator>
		<pubDate>Mon, 02 Aug 2010 12:08:10 +0000</pubDate>
		<guid isPermaLink="false">http://tobias.baethge.com/?p=844#comment-3108</guid>
		<description>Hi Chris,

thanks for the follow-up.

You are right, a user with editing rights can edit any table.
Unfortunately, this can not be changed. So, I&#039;m very sorry, but it sounds as if the plugin is not the right thing to achieve what you need. You are probably better off with a custom solution.
(One thing that might work: If every user of your site had his own WordPress (as a member blog of a WordPress Multisite Network), the plugin could be installed in each of those blogs and everyone would only be able to edit table in his blog.
Other than that, I don&#039;t see a possibility to achieve this in a single installation.

Best wishes,
Tobias</description>
		<content:encoded><![CDATA[<p>Hi Chris,</p>
<p>thanks for the follow-up.</p>
<p>You are right, a user with editing rights can edit any table.<br />
Unfortunately, this can not be changed. So, I&#8217;m very sorry, but it sounds as if the plugin is not the right thing to achieve what you need. You are probably better off with a custom solution.<br />
(One thing that might work: If every user of your site had his own WordPress (as a member blog of a WordPress Multisite Network), the plugin could be installed in each of those blogs and everyone would only be able to edit table in his blog.<br />
Other than that, I don&#8217;t see a possibility to achieve this in a single installation.</p>
<p>Best wishes,<br />
Tobias</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: chris</title>
		<link>http://tobias.baethge.com/2010/03/extension-7-textfield-widths-on-the-edit-page/comment-page-1/#comment-3107</link>
		<dc:creator>chris</dc:creator>
		<pubDate>Mon, 02 Aug 2010 11:54:19 +0000</pubDate>
		<guid isPermaLink="false">http://tobias.baethge.com/?p=844#comment-3107</guid>
		<description>That worked a treat. Manual method does the job just fine. Thank you.

We are working on a very large site and would like to use the plugin extensively. Essentially one table per registered website user. Each registered user can then use links (in their personal BuddyPress profile) to get to their personal specific table and update the content in their personal table. Only problem is, all registered users with editing rights can then update everyone else&#039;s table because there seems to be no role delineation between a user editing a table assigned to them and other users&#039; tables. Any ideas on that one? If I put it into perspective we envisage maybe 500 to 1000 live user tables, each assigned to a specific user with that specific user having table editing permissions - but what we need is that permission restricted to just the user&#039;s own table not everyone else&#039;s table. 
And again, thanks Tobias, for a wow plugin. We can see this setting the standard!</description>
		<content:encoded><![CDATA[<p>That worked a treat. Manual method does the job just fine. Thank you.</p>
<p>We are working on a very large site and would like to use the plugin extensively. Essentially one table per registered website user. Each registered user can then use links (in their personal BuddyPress profile) to get to their personal specific table and update the content in their personal table. Only problem is, all registered users with editing rights can then update everyone else&#8217;s table because there seems to be no role delineation between a user editing a table assigned to them and other users&#8217; tables. Any ideas on that one? If I put it into perspective we envisage maybe 500 to 1000 live user tables, each assigned to a specific user with that specific user having table editing permissions &#8211; but what we need is that permission restricted to just the user&#8217;s own table not everyone else&#8217;s table.<br />
And again, thanks Tobias, for a wow plugin. We can see this setting the standard!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

