Package Management issues: Revo vs Evo file directory

I installed as many components and templates using the Package Management tool in the System menu in Revo RC1.

Let me start with templates. How come all the templates have Evo file directories? Like Basic for example:


The actual link via the Files tab in the Manager tree:


Then SPForm suffers from the same problem. It was installed via Package Management, yet clicking on it’s link in the front end displays this fact:


Clearly that’s Evo’s file directory in both instances. Did I mess up somehow with installing these packages? For basic I changed the file path and it loads fine. I need to know if I’m doing something wrong before I can move forward with implementing Revo and developing tutorials for clients.


[tt]Operating Environment:
Apache/2.2.3 (CentOS)
PHP 5.2.6
MySQL 5.0.45
PDO_MySQL 5.0.45[/tt]

Templates are just examples, you can use the "Evo" style directory structures all you want, or not.

I don’t understand what you are talking about regarding the "actual link via the Files tab in the Manager tree". That is the package directory and is only used for installation purposes.

It’s possible you messed something up. But it’s really unclear what exactly the problem is in the first place, so saying the "same problem" for SPForm doesn’t help much.

By "same problem" I mean the same issue: The templates installed by Package Management doesn’t refer to their actual location in the Files directory.

By File tab, what should I call the Files tab in the left as shown in the attached screenshot?

Templates are just examples, you can use the "Evo" style directory structures all you want, or not.

What’s the point of Package Management then if it can’t install the package where it should go, such as SPForm? Why does PM create directory names like 7712e1c35bdbc2aa10a085fca1132166/0/ as in the case of the Basic template? Or was it me not having file permissions correct?

Thanks,
Peter

Quote from: Peter at May 14, 2010, 09:29 AM

By "same problem" I mean the same issue: The templates installed by Package Management doesn’t refer to their actual location in the Files directory.

They do, Peter. If you have the assets/ directory - specifically assets/templates - writable, as is required for Package Management, the files should be written there. The Extra that is being installed determines where the files will be placed.

By File tab, what should I call the Files tab in the left as shown in the attached screensho

Files tab.

What’s the point of Package Management then if it can’t install the package where it should go, such as SPForm? Why does PM create directory names like 7712e1c35bdbc2aa10a085fca1132166/0/ as in the case of the Basic template? Or was it me not having file permissions correct?

It definitely installs them where they are supposed to - whether or not you had the assets/ directory writable by the webserver is another matter.

Okay, this is making sense now, from a migration point of view.

I’m going to reinstall Revo onto an Evo directory structure and see if the PM does what you says it should do. Not that I’m doubting you, just that I tend to approach things as simply as possible

For example,the Revo Documentation doesn’t mention that I should have an Evo directory set up. Nor does the Installation FAQs and Troubleshooting. That’s not on you, it’s on me.

Update: I reinstalled Revo from scratch so to speak.

I created the Evo file structure so that the PM can install the templates into the assets/templates directory.

When installing Breadcrumbs I found that it wanted a components directory inside the core/directory. I uninstalled it, created the core/components directory, and successfully installed the Breadcrumbs snippet.

Is your test server able to create a new directory if one doesn’t exist? How come templates are looking for the Evo directory structure, but the Snippets are not?

I ask because I need to know if PM is working the way it should, or if my server is the issue.

Thanks!

Peter

Quote from: Peter at May 14, 2010, 11:15 AM

Is your test server able to create a new directory if one doesn’t exist?

Yes, I have my permissions set so PHP can create new directories.

How come templates are looking for the Evo directory structure, but the Snippets are not?

First off, there is no "Evo Structure" that you keep referring to. Whoever built that template package wanted to put their files in assets/templates. It was the developer’s choice.

You need to make assets/templates, core/components, and assets/components writable by the web server to use the packages in question.

You need to make assets/templates, core/components, and assets/components writable by the web server to use the packages in question.

Shouldn’t those directories be already created in Revo as part of the release? Not one of those 3 directories existed, and I’m pretty sure I had core/ chmodded to 777.

Thanks for the help

Quote from: Peter at May 14, 2010, 04:36 PM

You need to make assets/templates, core/components, and assets/components writable by the web server to use the packages in question.

Shouldn’t those directories be already created in Revo as part of the release? Not one of those 3 directories existed, and I’m pretty sure I had core/ chmodded to 777.

No; the core should never touch the directories component developers use to store files. On some platforms this can severely complicate upgrades, and as splittingred noted, these are not core-related directories.

Some improved error-handling on the package installation to warn users of these problems might be in order though.