Fork me on GitHub

Re: So, what about front-end assets?

Good question Personally I feel that composer is very good for the purpose it is built : manage PHP packages and the dependencies between them. Where it comes to front-end assets (CSS, Javascript, SASS, LESS, TypeScript, ...), composer lacks the full feature set that is needed today.

Most front-end developers nowadays user LESS or SASS in their workflow, and they have grunt or node.js or gulp systems setup to compile, rework, minify and zip the resulting files into the most efficiënt package possible for web consumption. I think we should leave that part to the designers and front-end developers, because that changes so often and it's really different technology.

ImpressCMS doesn't handle included files well at the moment. If one day there would be a way to interactively define the different files to include through the core (on server or remote), it would start making sense to try to manage them in the core, but not before.

Topic


So, what about front-end assets?

ImpressCMS 2.0 will come with composer out of box. So, installing PHP modules and libraries will be easier, but what about front-end assets? Do you have idea?

...so do you? Would you like to share your own opinion here -> https://github.com/ImpressCMS/impresscms/issues/134

Yeah, I know that this question is on GitHub, but I think this is a better place for talking about any development issues :)

Topic


1.3 talks, PR and roadmaps

Are you communicateing much between each other... during coding /development? ## I saw that Sato seems to relax after, was it 1.3.2 or somti'n. ## I think we now can keep climat more cool and planned around here now. When this template thing is solved, that is. ## Is there any discussion about roadmaps? /MG /JN /WN (since ~2007, I think). Happy and rising 2018!



Re: Smarty resized_image plugin: update

It needs to write thumbnails to cache or templates_c, I forget which. So another possibility is if those aren't writable for some reason it will crash out.



Re: Smarty resized_image plugin: update

fiammybe, I think it's related to PHP-GD lib. From the code what I see it's only possible to get empty response if resizing image or getting image info fails. Can it be that PHP-GD is missing on server? Also, it's possible that WideImage fails. idk, why there is methods in the code from GD lib and WideImage...



Re: Smarty resized_image plugin: update

I'm resurrecting a very old post, but is there a good explanation on how to use this image resizer? I've tried it on a site, and I get blanks instead of an image URL...



Re: New Vagrant box for developing something with/for ImpressCMS just released! v0.1

That worked! Thank you @mekdrop

Steve Twitter: @skenow Facebook: Steve Kenow



Re: New Vagrant box for developing something with/for ImpressCMS just released! v0.1

@skenow this is a correct way now to do that -> dmFncmFudCBwbHVnaW4gaW5zdGFsbCB2YWdyYW50LWltcHJlc3Nib3g= :)



Re: New Vagrant box for developing something with/for ImpressCMS just released! v0.1

when I run dmFncmFudCBwbHVnaW4gaW5zdGFsbCBpbXByZXNzYm94 I get this error

Quote:


Bundler, the underlying system Vagrant uses to install plugins,
reported an error. The error is shown below. These errors are usually
caused by misconfigured plugin installations or transient network
issues. The error from Bundler is:

Could not find gem 'impressbox' in any of the gem sources listed in your Gemfile or available on this machine.

Steve Twitter: @skenow Facebook: Steve Kenow





Re: New Vagrant box for developing something with/for ImpressCMS just released! v0.1

Small update: I have just released 0.1.1 version with bug fix when binding IP, so now it's possible to have one IP linked to own development box.

Page for new version is here -> https://t.co/SaQfs9hUj9



Re: reskin admin pages within a new theme

Bug !

Hehe, Murphy came around the corner here, it seems I was testing with a page that doesn't work as expected. Other pages work all right, so I did ticket #922 and resolved it for the upcoming ImpressCMS 1.3.10 (see PR 67)



reskin admin pages within a new theme

I'm trying to define a different template for an admin page in ImpressCMS 1.3.9. I was hoping this would work the same way as for the normal pages : you define a template file with the same name in your theme in the correct subdirectory, and the system takes that file before instead of the standard template.

I was trying with the file system_adm_adsense.html for the adsense entry in the system admin menu. I've made a 'admin/adsense' and an 'admin' folder where I placed a changed file, but I don't see the changes.

Is this kind of reskinning supported in the admin?

I had a look at http://community.impresscms.org/modules/newbb/viewtopic.php?viewmode=flat&type=&topic_id=4880&forum=55 but there is no real solution described...



Re: New Vagrant box for developing something with/for ImpressCMS just released! v0.1

Succes! For the record, using this combination is dony by the following commands:

dmFncmFudCBwbHVnaW4gaW5zdGFsbCBpbXByZXNzYm94ICYmICB2YWdyYW50IGltcHJlc3Nib3ggJiYgdmFncmFudCB1cA==

The site is then available on your localhost.



Re: New Vagrant box for developing something with/for ImpressCMS just released! v0.1

If you use also *vagrant-impressbox* plugin, you can access web by typing http://localhost in your browser. Also, sometimes other app can use same 80 port, in that case check what `vagrant up` prints. On what port web is running.

If you don't use this plugin, you need to modify your Vagrantfile. How to do, there is info on vagrantup.com website.

----

Some other usefull tools that exists when you boot this box:
http://localhost/phpmyadmin - phpMyAdmin
http://localhost/md - Memcache admin



Re: New Vagrant box for developing something with/for ImpressCMS just released! v0.1

It seems my vagrant setup was a bit botched up, I reinstalled vagrant, after a complete wipe, and everything seems to run now. I don't know how to access the impresscms site that's running in the VM though. Can you give me any indication?



Re: New Vagrant box for developing something with/for ImpressCMS just released! v0.1

I tried this, while updating from 0.0.3, and I got this list of error messages on the insert_key action. Newly installed Vagrant on Windows 10. I've created a bug report.



New Vagrant box for developing something with/for ImpressCMS just released! v0.1

If you are trying to develop something with Vagrant with ImpressCMS, you can try to use our official box.

Few days ago 0.1 version was released. This release is based on new Ubuntu 16.04. Also that means that this release comes with PHP 7 only! Also, this release ships with build-in self-updating ImpressCMS code, so if you do something wrong with it, you can simply just delete www folder and wait a bit until local ImpressCMS installation is restored.

More info about this release could be found at
https://atlas.hashicorp.com/ImpressCMS/boxes/DevBox-Ubuntu/versions/0.1.0

If you have any suggestions or/and found some bugs, you can create ticket(s) here -> https://github.com/ImpressCMS/packer-impresscms-devbox/issues



Re: Vagrant box for ImpressCMS

Thanks for the update! I'll try to use this vagrant to build releases. That way, setting up that kind of infrastructure should be much easier.



Re: Vagrant box for ImpressCMS

New version for box just released - 0.0.4!

The change log and example how to use it can be found at https://atlas.hashicorp.com/ImpressCMS/boxes/DevBox-Ubuntu/versions/0.0.4

Also, I have updated https://github.com/ImpressCMS/impresscms-vagrant-template to use only one configuration file. With it is easier to start to develop something in your local machine.




 Top