Soma

Can't install. 2013-01-12 23:03:28 admin pwprofile/processwire/module/ Parse Error syntax error, unexpected ')' (line 78 of /Applications/XAMPP/xamppfiles/htdocs/pwprofile/site/modules/ToolsTimeAgo.module)

Ok got it back working with 2.2 1.0.4 - added back support for PW 2.2 - some maintenance

I don't know, anybody else got same issue? It's working fine.

I discussed and almost went for it, but abandoned it. It's possible already to put it outside into your site folder, but then you'll have to maintain it. I also thought this same thing as you but somehow I'm still not sure it's the way to go. SInce it will be shipped anyway I don't get the argument of size. I ran this setup with 3-4 projects in the past to be able to change some code that will help include custom plugins from within /site/ folder. Since this is now in the core Tinymce, there's no need anymore. Also since there will be some changes soon Ryan said in the future we want to support other editors, I think this would have to be considered by then.

I'm not sure manifest is the right word. I mean make up some conventions that will help making the install process more convenient. That would contain certain infos about the version it's compatible with maybe important update instructions along with the version, currently it's done via modules.processwire.com which is cool but not enough.

Thanks Ryan. I'm still up with including Modules Manager in the core, but I'm trying hard to imagine how to go for it and what all the features are that are absolutely needed and super important. We discussed this already some in this thread and I still couldn't make up my mind thinking about it. However One thing is sure that it should still work the way it is now and let you install modules without internet access (local environement). But the way it works now this is already possible and it is no problem I think. √ I don't think an alternative "upload" function via a form is a good way, as you already can put it manually in such a case (already have it locally for example) Now working on the module a little and thinking about versions. How should we handle this all if at all? Module Version: There's a module version that have to be different to recognize an update and output a action link according. By now it just replaces the folder. What if the new version doesn't work and. In short, would some version management make sense here, with rollback etc? I think this would be harder and a lot more work to implement. But also thinking about managing modules through such a interface with direct downloading may really need such features as a "manifest" for the module with update instruction that can be displayed while installing and make some of those thing required for PW modules. Rather now than later. Currently there's no way to implement a good system without it. There's some idea's but I can't make it up myself. Module PW version compatibility: On modules.processwire.com you can select for what versions of PW the module works. Which is cool. But currently when there's a new PW version option there like the 2.3, almost all modules don't have this checked. So now checking for the version on PW locally and the ones of the modules wouldn't work so well as there're only one of mine that has it checked. What you think? Some soft notification that it may not work? Not really. But I don't see a nice solution to this issue, maybe otherthinking it.

Thanks @Ryan. Looking at my module again, I seem to have missed that I already have a recursive remove dir function I used. I just forgot about since it's some time ago already I implemented that. Baaah, shame on me I'll update the module again to correct that. Yeah for future version. It's might be cool to have a version check to see if a module support the installed PW version. @Nico. I'm not sure. Does the zip extract not work for you? I already have a much simpler zip extract function, but thanks anyway. At least, it remembers me to implement DIRECTORY_SEPARATOR too.

How about adding it to modules.processwire.com?

@Joss, I think I know what happens to you. Version is the latest version of the module. Status is the version you have installed. If you update and it says it's sucessful, but the status still shows the old and an update link there must be a write permission problem. It have the same issue in my local testing server (don't know how to correct the permission really), when I have a module that I installed manually originally and try to update it via modules manager. So it seems you have the same issue. What I have to do in this case is change the files permission to be writeable and it then works.

Ups. Pete is right it requires 2.3 because of new remove dir function. Completly forgot about it. Hm not sure what to do Should I remove it? Joss Im not sure whats about that. Is it working or not if you update it?

I always use screenomatic online screen recording. It is free and you can directly upload to youtube or computer. http://www.screencast-o-matic.com/

little update, big improvements afte little more testing. 1.0.3 - Language Packs and Site Profiles now show up but will have a "more" link to the repository page. - Added check if no download github url found to give a "more" link to the modules url

Omg what did I do!! Now I cant decide which one and am constantly swizing between them... No but it's fun and makes it easy and interesting comparing them. Some need updazes.

Or LegoWire

I'm so sorry Ryan, this wasn't intentional. But I could record you a video you can watch on your mobile

Just had to implement admin theme install feature in ModulesManager to more easily install because I'm lazy dog.

Added support for Admin Themes install. Let me know if it works for you. It's now updated to 1.0.2 and can be updated using Modules Manager, just refresh the cache and go. Thanks Adam for reminding me implementing it! - When installing it, it will throw a JS confirm as it will delete the templates-admin folder in site/ when found. - It will look for a folder templates-admin in the downloaded folder and install it, or if not found it will move the content of the extracted folder to site/templates-admin (assuming it's already the templates-admin folder). Thanks

Those were the times where I could remember all admin themes out of my head Great theme btw.

(We already discussed this Joss in an other thread? I still think using a special ProcessModule to create admin menu would be a great way. Like having a menu "Add" and subpages "News, Article, ...". But since default admin still has no pulldown menu it would only work well with themes like teflon. I was thinking a little about other alternatives and I think it would be easy to build a module that let's you add entries to a url in the backend to add , but haven't found a good idea where to add the "menu" and of what type.) My personal thinking here is: Why add this whatever dropdown if you already have the most easy way to add a new page using the page tree. And it is in the same manner for all content and as you do it with all pages in PW. Once the user knows it, he knows it and it's consistent and gives a "ah it's there in the page tree" feeling you don't have if you have one big button somewhere that says "add Blogpost". If you mix these things up to much you "un-educate" the user a little and he will come every other day to ask where to do this and that. If you get what I mean. My experience with non-technical users and PW admin, so far is really, really great and they just get it first time. Never really had support with these things, and I'm a strong believer in the simplistic approach of the admin and it's flow. Clients told us they're really surprized and love the way it all works together. I think adding noise to the admin in form of buttons and features will hurt these balance. I know Ryan built it this way for a reason, it's not something that he forgot or is not possible. I believe many new devs that try out PW first time are thinking "there's nothing, so it can do nothing"... They seem to be infected by other systems that go the opposite route and hardly understand flow in a application anymore. Also maybe this should really be part of a bigger modules that add a dashboard like admin page where you could add such things. MadeMyDay's dashboard has this functionality in I think.

Who uses php 5.4. Seriously I wouldn't be able to use this module and many others too. Thanks for removing it.

Hey, I already provided the code previously http://processwire.com/talk/topic/2506-running-a-daily-newspaper-website-with-process-wire/#entry23926, with a hint to http://simplehtmldom.sourceforge.net/ which makes parsing the files and the html tags a breeze.

Looks like the php version required is 5.3 here. What do you have?

What do you think why I posted that?

Are you looking for this? $t = new TemplateFile($config->paths->templates . "./{$page->template}.php"); $t->set( "hello", "hello world" ); $t->set( 'input', $input); echo $t->render();

Great adam, thanks for the plugin. There's seems to be a lot of tree/label plugins lately that could be maybe merged together, not sure that would work or make sense. I'm not too sure about the various string configuration as being to complicated. Also I think the the Module name is strange: "..Better.." is that really needed?