Architecture / Installation

Posted by thebookdoc 10 Mar 2009 15:57 GMT-0000 posts: 26

As I continue to plug holes, some clues arise as to the problem...the issue seems distinct to buttons with a relative path (other relative paths like Links work fine). For example, in the same template you have:

Does not work:

{tr}Structures{/tr}

Works:

Yet these links work:

{if $remove eq 'y'}
{tr}You will remove{/tr} '{$removePageName}' {if $page_removable == 'y'}{tr}and its subpages from the structure, now you have two options:{/tr}{else}{tr}and its subpages from the structure{/tr}{/if}
{tr}Remove only from structure{/tr}
{if $page_removable == 'y'}
{tr}Remove from structure and remove page too{/tr}
{/if}
{/if}

Posted by davenh 04 Jun 2009 12:11 GMT-0000 posts: 6

I had the same issue running Apache in Windows, and I think I found the issue..

In /lib/smarty_tiki/block.self_link.php, replace the following:

$self_dir = dirname($_SERVER'PHP_SELF');

with this:

$self_dir = str_replace('\\','/', dirname($_SERVER'PHP_SELF'));

Posted by Marc Laporte 04 Jun 2009 15:10 GMT-0000 posts: 1633

It is unfortunate that you are feeling this way.

Let me give you a bit of background information. This will not solve the technical issue in the short term, but I feel I must react. I think being pleased or disappointed has a lot to do with expectations.

I feel your expectations are not in line with the context. 1st off: Tiki is a project not a product. There are no employees, only volunteers in a community. People here are scratching their own itch and choose to share back. All the people here are giving their time, and they don't owe you anything. Very much the way that you don't owe them anything. You are just as responsible as everyone else to solve this problem.

There are hundreds and hundreds of items on the wishlist at:
http://dev.tikiwiki.org/

If you want a product or a service, and the associated quality of service agreement then, you should (and I am pleased that you are ready to) hire a consultant. I hope that you choose to go the extra mile and get the issues fixed and shared back to the project.

Who says this is a Tiki bug? It could very well be a Microsoft bug. Have you complained to Microsoft because the program is not working like it should?

About misleading claims:
It obviously works for some people. I regularly install Tiki with XAMMP and it works very well. This is a wiki project so please do update the documentation to what you feel it should be. It's no use to attract people to the project that will be unhappy. This is not a bait-and-switch strategy.

Tiki has more built-in features than any other open source Web application. This has benefits and challenges, one of which is the varying quality of features. Make sure not to turn on experimental features, like Search Engine Friendly URL. This feature is relatively new and may be causing issues for some people.

On a related note, I recently started a project:
http://dev.tikiwiki.org/Operating+System+independence#Windows_compatibility_project

Best regards,

M ;-)

Posted by thebookdoc 22 Jul 2009 14:52 GMT-0000 posts: 26

I hadn't seen your response before as a public piece Marc, but I feel I should respond as well...

"I feel your expectations are not in line with the context."

The context is that the project/product is advertised as compatible with Oracle and Windows servers, and none of the developers use either of these. Your development team, whether volunteer, martian or monkeys typing, should claim only what has been tested and is known to work. That is not at all out of line with decent expectation lest someone using Windows servers and Oracle be lured in to waste thousands of hours trying to get a product to work...

"You are just as responsible as everyone else to solve this problem."

That might assume I am a programmer able to define and make the change. Are the people using this 'project' only supposed to be programmers? If so, mention that in guidelines for use. I am alerting the community to a problem, and to me that is a rational action and the way in which I can probably best help the community, rather than hacking code that I don't belong in.

"Hire a consultant."

Who if they are allowed to make changes in code (as everyone is) might have motivation to smear it so that their services could be worth more to more people.

"Who says this is a Tiki bug? It could very well be a Microsoft bug. Have you complained to Microsoft because the program is not working like it should?"

Inconsistency and a lack of standards seems to have led to this issue. Well-formed code would not have the same inconsistency.

"About misleading claims:
It obviously works for some people. I regularly install Tiki with XAMMP and it works very well."

I don't doubt it works in particular environments. List those that have been tested in the product claims. Not those that have not. This is responsible reporting that will keep people from expending inordinate amounts of time trying to get something to work which has overt claims of being proven, when it has not.

Tikiwiki does not have to claim to be everything to everyone to be valuable.

RL

Posted by Gary Cunningham-Lee 23 Jul 2009 03:51 GMT-0000 posts: 4656

To add to what Marc said...

My perception is that database/OS compatibility was more complete in earlier Tiki releases, but gradually the code has gotten more MySQL-specific due to the interests of the people involved, and the feature lists (especially on other sites) haven't been updated to reflect this.

Of course the great majority of users aren't programmers, but I think Marc is talking about the process in a community of volunteers who, if they are programmers, mainly are already very busy with their own todo lists. The project benefits by this coincidense of needs and solutions. People with needs, who aren't programmers, then have the option to...

I can't imagine this scenario happening. Anyone who would be that malevolent probably has bigger fish to fry, and anyway code contributions (I assume the fixes would be contributed to the code base) are watched carefully enough that "smears" would be spotted.

Though you say you aren't a programmer, if you are aware of problems in the code (or if anyone is), if you report it specifically as a bug, that's a good contribution to solving the problem.

Personally, I think the supported platforms on some of the wiki-comparison feature lists have become inaccurate over time, which is more a matter of negligence in keeping them up to date rather than anyone being willfully misleading. But apart from those lists, I'm not aware of "overt claims of being proven" that Tiki will run flawlessly on IIS and Oracle.

There've been efforts recently (introduced by Marc, mainly) to either bring support for these other databases and OSs up to speed or to accept that there isn't sufficient interest by present and would-be participants to do that, so this is an issue that the dev community is aware of and working on. The PostgreSQL community was approached, for example, and there have been results (code commits) from that. Unfortunately, not much happening about IIS as far as I know, which may be telling.

-- Gary