Re: Blocks that are URL aware

Still more - SymLinks allows you to define 'visible in' pages for any URL. For your situation, though, you'd still need a block for every page. You're going to have to deal with this for almost any option to have different content based on the URL. Once built, it should be fairly easy to maintain. Sign in, go to the page, click on Edit for the block, edit and save.

Topic | Forum


Re: Blocks that are URL aware

Just brainstorming other alternatives - use a custom block with type PHP. It might be a bit of a chore to figure out all the parameters for each module, but it could be done. Use icms::$module to determine which module it is, then specific branches to process the individual pages of that module. How you would assign content to the block based on the module + page and easily be able to change it... challenging. Custom tags could be used, too.

All in all, I'd default to SimplyWiki for everything.

Topic | Forum


Re: Blocks that are URL aware

What you describe is something SimplyWiki does using 'SideContent'.

The concept is to create content related to the main content and assign it as the SideContent for the main page. Then, enable the SideContent block and place it where you will. Based on the page being viewed, the SideContent block displays the content of the page specified as SideContent for the page.

You can see this in effect at www.design-n-bloom.com - visit most of the pages in the menu bar and the block labeled "More Information" is the side content block. 'Send Fresh Flowers' and 'Plan Your Wedding' are the 2 main examples.



Blocks that are URL aware

Hi,

I want to add a image block to every page on a new site, along the likes of https://www.oudervereniging.be/. I would need the same layout for content, event and blog pages

  • with different images for each page
  • without tens of duplicated blocks
  • Without needing to update the individual modules

My idea would be to re-write the existing billboard plugin and make the block page-aware. Is there a way to retrieve information in a block concerning the module and the page the block is shown?

In that case I would handle the images ona page-by-page basis.



Re: Visual upgrade of the installer based on Bootstrap

I put this one temporarily on hold, so I can help get 2.0 out the door.



Re: imTagging module - do tags work?

OK, it looked like it as well, but I wanted to be certain.µ

I'll see if I can add that part easily, otherwise I'll remove it from the upcoming release and put the relevant code in a branch for later inclusion.



Re: imTagging module - do tags work?

That part of it was never really finished, I believe.



imTagging module - do tags work?

Hi, i'm trying to integrate imtagging into the events module (https://github.com/IsengardBiz/events) and I seem to miss the function that stores the link between a specific tag and the current object. I'm not a real user of that module, so I'm asking myself if that functionality is working all right within the imtagging module?



Re: Standup Reports

I'm encountering errors in PHP 8.1 with the 'count()' use in some IPF instances. I'll create tickets and see what I can come up with.



Re: Standup Reports

Those updates have been applied. Now, in testing on PHP8.1, I've discovered another update is needed - HTMLPurifier. Again. I'm not sure how this was missed. It looks as though I tested it locally and never pushed the proper files to github.



Re: Standup Reports

During my final tests, there were some things we needed to address before releasing.

A couple more merge requests - an update to the GA4 plugin because it used a legacy class name and has a fatal error in 2.0. And, a final fix to the image editor so the plugins work now! (crop, resize, and filter were broken when using PHP8+). The changes for the theme selector block have also been approved are are ready to merge.

Once these have been merged, we can package and release 2.0RC!



Re: Visual upgrade of the installer based on Bootstrap

Yes, that was it. I think that was prior to the all the disagreement over the refactoring of the UI and assets. There is another branch that was based on the 'retro' branch that came out of it. https://github.com/skenow/impresscms/tree/features/installer2.0

 





Re: Visual upgrade of the installer based on Bootstrap

I still have the work we started to update the installer which was mostly a single page.



Re: Visual upgrade of the installer based on Bootstrap

Probably because I didn't get further than that page on the mockups. I've been trying to get it to work in an actual installer, and I've gotten as far as the creation of the admin user at the moment. So it's proceeding in the right direction. 



Re: Visual upgrade of the installer based on Bootstrap

It's looking good, David! I wasn't able to get past the DB connection page in the mock-ups, I'm not sure why.

Looking forward to adding this to our upcoming release.



Re: Visual upgrade of the installer based on Bootstrap

Progress update : the base design is running, and I'm currently implementing the specific changes that are remaining page by page, while testing that the functionality remains. Currently, I'm stuck at the paths page - you can't create a trustpath.

I think this will be ready for test in a few days. PR will be incoming soon.



Visual upgrade of the installer based on Bootstrap

I am working on mockups for the installer. I'm not ready to rewrite the whole thing, but in the short term I can make sure it looks more up-to-date than the original MrTheme design. I'm still making mockups before I will start updating code, but this is where I'm at at the moment. I have the mockups available at https://beta.impresscms.eu/install2/index.html at the moment. Have a look around and give me your feedback.


Attach file:



png  new-wave-mockup.png (134.35 KB)
1102__2877364cec5cc084cc.png 2644X1217 px


Re: Standup Reports

Hi, 

  • I updated the PR for the GA4 preload. I took the one from ImpressCMS 1.4.6 for consistency.
  • I merged the approved PR for 8.1 compatibility.

I think we are ready for a 2.0 RC.

 



Re: Standup Reports

A patch was released for GA-4 for 1.4.4 and 1.3.11, as well as a new release - 1.4.5, specifically for the GA-4 update.

Things in progress -

  • The PR for the WideImage update is still waiting for a review. The issue with the editor still persists. I don't think it's a show-stopper.
  • The PR for the GA-4 update differs from the patch released and the 1.4.5 release. I propose we use what has been released. We could
    • merge the existing PR and then modify;
    • update the existing PR and then merge;
    • withdraw the existing PR and submit a new PR with the plugin from the 1.4.5 release
  • There is a new PR to update the installer to be compliant with PHP8.1. Review has been started.

I've also been looking at the HackerOne reports and working on prioritizing those for upcoming releases.




 Top