@Sebastian-Roth yep, both with the new ones.

I’ll do a debug run next week and check the messages, and I will check the flags as done in https://github.com/FOGProject/fos/blob/master/Buildroot/board/FOG/FOS/rootfs_overlay/bin/fog.upload#L109 - I did not “play” with the flags manually, but I will compare to a brand new Win10 MBR installation if the flags got mixed up.

Other question: could I just change the d1.fixed_size_partitions to

:1

as long as my source file system was “small enough”? I actually prepare the images on a virtual machine having the VHD slightly smaller than the smallest target system SSDs we have in use.

Normally, I prepare in the VM, deploy once to each target platforms, check the drivers and then capture each platform. Right now, we have 4 different models in our department (~30 to ~90 per model)

@Sebastian-Roth I am using the new inits, and right now, it seems there is no resizing at all.

If I redeploy an image of a MBR based system, it has exactly the same size as on the captured one. On the other hand, there is no “fixed partition” message on the screen, but also no resizing message.

Content of d1.fixed_size_partitions

:1:2

Content of d1.original.fstypes

/dev/sda2 ntfs

I’ll switch back to the original inits, but if there is anything I could provide to help debugging, please let me know! Or could there also be an issue because of our local naming policy naming “System”, thus being confused with the UEFI “System” partition of GPT based systems? I didn’t check the sources yet

@Tom-Elliott That’s what I tried the last two days, I am literally “poking in the FOG” sources I more or less got the backend part with FOGPage, FOGBase, FOGController and most of the reflections used, but the JS frontend is a bit mysterious from time to time…

Lets e.g. use this form as an example:
https://github.com/FOGProject/fogproject/blob/348f695c3def03050877c4919e2041f2cf91b965/packages/web/lib/pages/storagemanagementpage.class.php#L1316

What does it make to use AJAX? There is some jQuery magic going on to prevent the default submit event, that’s pretty clear. Unfortunately, it is hard to find out why this is happening. Right now I am assuming setupTimeoutElement() is setting the submithandlerfunc to intercept the form submit, and then one is doing the AJAX stuff?

I’ll give it a try on my dev machine tonight…

Hi everyone,

for our new local plugin, I am using a single page without PAGES_WITH_OBJECTS, as we have several different database entities to manage on that one page. I had to look deeply into sources but got it almost up and running.

I noted that there is some hook (I think in the fog.js part) to get “normal POST forms” to work as AJAX forms and it seems to be related to action boxes and PAGES_WITH_OBJECTS.

This brings me to my quick question: how can I use AJAX forms on a more generic page?

Thanks and BR
Martin

@flipwalker +1 for your question no. 3

I also noted that behavior, and considered it as a configuration issue because we just started to deploy multicast on our core routers and switches. We want to deploy with multicast (ee have 1180 clients in about 50 lab rooms) and manually joining a session is quite annoying even in only one lab room.

Hence I am willing to to dig a bit in the source code - if someone has an idea where to start I’d be thankful!

BR
Martin

@Tom-Elliott ok thank you. We are starting with doing only some basic things, so I will just continue to get it up and running on 1.5.x.

Right now, I am using the doxygen generated focdoc/ folder and mostly some examples in other plugins. Sometimes a bit tricky, but IMHO no need to generate the files for 1.5

@Tom-Elliott
Hi Tom, I am just starting to develop an internal plugin for some data we need to handle for our client computers and want to assign to hosts and groups, so that this data can be accesed both via FOG management and FOG API so that we have this info to be used in our snapins.

I did not go very deeply into the sources of FOG yet and just started by checking the example plugin and some other plugins to get a feeling how to do things, (coming from the Laravel world…).

As I am not familiar with all the hook-event thing yet: does your post mean there are any significant changes in the plugin system coming in 1.6 - at least changes which would break a plugin developed using 1.5.x?

@Sebastian-Roth does it make sense to test these init files also with 1.5.5 stable? If yes, I’d be willing to test as I ran into the “resizing” issue just a few days ago having “System-Reserviert” as partition label on some of our Win10 Edu German master images. It took me days to find out that the boot loop indeed was not an IDE/AHCI ang buggy BIOS issue, which we had before on some point as well…