www.wysiwygwebbuilder.com

i tried the last version 8.1.5
it seems there is an issue loading the new jquery version... but not in all projects!
i tested locally the demo online and is working fine.
i will see to make a workaround for this as soon as i can. please note that the issue is not a my end.

Well, I am very sure that the issue is not with your extension. I also get a missed stuff showing in timed event script you provided me earlier with this version.
I posted these issue in the "General" section for Pablo to know, and here is the link if you are interested to know what Pablo would say about it:
viewtopic.php?f=5&t=47807
And please [RZ] don't waste your time to make workarounds for this issue, especially for ME, I can live with version 8.1.0 until Pablo finds out the fix for this issue.

Again, thank you so much for clarifying things

well, i have a fix in my hand, but there is a minor minor really minor issue in the generated code by 8.1.5
post a workaround, then re-post a rollback will be time wasting.
i think pablo will fix it really soon.
there are a lot of extensions that depend on this.

Thanks [RZ].

I read your post in the thread I provided. So yes, no need for the workaround at all will be waiting for Pablo to make this fix

Thanks you

i think pablo is working on the reported issue.
anyhow, i did a temporary fix for the mean time.
just download the fix here: (***link removed*** the fix is now obsolete)
install it, and drag and drop it as a normal extension, once the issue is solved, you can remove it from your page, uninstall and delete it.
best regards to you all.
this fix may also be a temporary solution for all my extensions (if you are experiencing troubles).

*** EDIT ***
good news!
fortunately, i've read the issue was already fixed by pablo.
anyhow, once i receive feedback that all is working normally, i will be removing the fix as it will become obsolete.

*** EDIT #2 ***
link removed, now it is obsolete and all is working fine!
just be sure you redownloaded the *last* version.

Hello [RZ],

I didn't download the fix you mentioned, but installed WWB 8.1.5 after I read your post in the thread there where you mentioned that Pablo fixed the issue, and YES, everything is working as before

Thanks a lot for helping and giving some of your time to discover the issue and come up with a temporary solution

Hello [RZ], am back

Just wanted to inform you about something (I don't know if it is an issue or this is how this thing works) which was there from early versions of your extension.
I have "oc" extension with a base layer, and the main layer is transparent. Now inside this transparent layer, there are two layers on top of each other which are connected to the "pagination" extension.
If I drag a text as an example inside one of those two layers (basically the one on top) the text gets separated from its border, and this happens to any other objects I try to drag inside the layer.
I am currently on version 8.1.5 of WWB and 1.6.0 of layers extensions. (The above issue also happened with older versions of WWB and layers extensions).
I attached a ready-to-test sample, all you need to do is to drag the "DRAG ME...." text object inside the green layer and see what happens.

Thanks

*****EDIT*****
Well, I know this has nothing to do with your extension, as I tried something without your extension; it seems nesting 3 or more layers inside each others generates this issue!

i didn't download yet your project file, i will see at it, nesting layers in edit mode, you may get strange behaviors, this is well explained by pablo.
anyhow, you can deep nest layers with my extensions, but be extremely careful on how you edit your project, nest them visually only, but hide the base layer while you are positioning the layers that will be over the container in order to not nest them. layers are a concept in wb, are objects containers, not simple divs...
i will be back in two hours with an answer about your posted project.

if you want to nest layers, lets say because you have visual structures that want to hide/show simultaneously, don't worry, move these layers to be nested to a masterpage, and include this masterpage into the layer container.

i looked at your project, it has a visually issue, but behaves well in run time.
this is because of the layers nesting, but as i told you this is well explained by pablo.
move the layers to blank pages and include them as masterpages, this will solve all of these issues.
and know that the project you posted is working really fine, as expected.

Yes, this is well mentioned by Pablo but I just wanted to make sure. And thanks a lot for the masterpage solution, I will try it.
The project works well as you mentioned, it has only this visual thing in design mode... Thanks a lot for helping

[RZ]
Managing the project with masterpages is much easier, so thank you so much for this tip

so glad to know it works better for you now.
thanks for give feedback on the matter.

Hello again [RZ]

Well, I just want to ask this to see if it is easy to do, if not, then please let me know... Here is the case:
I put some objects (images and text) inside a layer. These objects will perform some CSS3 transitions and they work %100. These transitions take around 16 seconds to finish, and upon the finish, I set a timed event (just like the one you provided me) to open the first "oc" extension (which will be on second 17).
Since the 16 seconds transition is long, I added a text "Skip Intro". On clicking this text, the layer containing all the objects will hide and open the "oc" extension. BUT, since there is a timed event at second 17, this "oc" layer will close and open again! And here comes the question:
Is there any easy way to disable the timed event on second 17 when clicking "Skip Intro"?

Hope I described everything well.

Thanks

the OC extension has a prevention to not re-open itself.
you can trigger 1000 times the opening sequence, but only the first one will take place.
try it by yourself:
add a dummy text to be used as a link
in that link add an event like: MyObject_open();
preview and click repeatedly on that event/link...

so, don't worry about re-re-re-opening...

Thanks a lot for replying that quick
As I need to leave the PC right now, I will try it when I get back home and let you know
Thanks a million

...and about the timed sequence interruption, i need to know how you implemented that intro.
but i think it may be resolved with relative ease...

[RZ]
Shall I attach a sample project to show you what I exactly need?

*****EDIT*****
Yes [RZ], you are right, clicking "Skip Intro" will trigger the javascript to open the first "oc" extension (Extension1_open();), and the timedEvent to open the same extension after 17 seconds will not take effect.
BUT, I forgot something to mention (sorry ), if there are 2 "oc2" extension synchronized together, and clicking on "Skip Intro" will open the first "oc2" extension, then I click on the second "oc2" extension (which will open), on second 17, the second "oc2" will close and the first "oc2" will open again... That's why I am trying to find a way to disable this timed event on second 17 as I click "Skip Intro".

I prepared a sample, I can attach it here if you want.

Thanks

just an idea.
it seems you are using an intro in the same page you have the main site.
so, i suggest you to do a small change.
make your intro, while you have the [rz] Preloader (http://wysiwygwebbuilder.com/forum/view ... 42&t=46020).
set the preloader to 17 seconds.
if the user clicks on the skip intro, that is the link to the main page, will be redirected to your main site.
if the user doesn't click, anyways will be redirected once the intro is ended.
i think this way you can get rid of more complex procedures.
besides this, after the intro, the user will be redirected to the main site, and because it was loading itself while the intro is shown, will see the main site shown in a snap.

well, in my previous post i forgot to mention something...
sorry, i didn't neglect your intention to post a project, i think there is no need for that.
you can follow the method i posted as an alternative.
but you may insist on how to cancel a timed event, like some time ago i told you how to trigger them...
there are some reasons to get rid off from more complex procedures, the preloader extension gives you a first solution, anyhow, the way to cancel a timed event is as follows:

1. "register" the timed events (just an example, values may vary of course):
var proc1 = setTimeout('myfunction1();', 1000);
var proc2 = setTimeout('myfunction2();', 5000);
and so on...
2. lets say if a condition is true in myfuncion1(), and want to cancel the event called myfunction2, just do this:
clearTimeout(proc2);

i suggest you to use the first alternative, you can easily mess up the things with this method.
took me a lot of time all the required testings to fine tune the timed hide/show process in nested hidden/visible layers (explain all this stuff is far beyond of this humble extension/thread).
and on the other hand, my first suggestion will free up the computer's resources of your potential visitors, especially on mobile devices...
just my cent.

[RZ], thanks a lot for the new suggestion, I really believed that I have to use your preloader extension, but now I think it is a must
Also, I will try the other solution... Well, actually, all my site is on the same page organized by your layers extension, so that's why I would like everything (even the intro) to be on the main page.
Anyways, here is the a sample project of what I intend to do, just for you to know how I would like it to be.
Thanks a million for the last two posts, I will read them carefully and let you know how it goes.

the method you implemented, "seems" to be fine.
BUT unfortunately you will run into many downsides.
you have a transparent shape over the two OC2 extensions.
well, you cannot make any click... seems ok, right?
but what about the tab key and the enter key? your method falls...
this is only one of the reasons i said you that you may be messing up many things...
let's say you have properties like "locked" or "inactive", anyhow you must handle too many things.
so... to make the things simpler, i would make the intro and the site in two individual pages; of course, with the preloader.

(ps: don't try to make a flash-like site, also flash sites sometimes has individual sections that are loaded on-demand)

[RZ] wrote: you have a transparent shape over the two OC2 extensions.
well, you cannot make any click... seems ok, right?

Yes, I put that because I want the transitions to finish first, then the transparent shape disappears so visitors can now click the links. And, the only way to click them is to click "Skip Intro".
And I guess the Tab and The Enter keys work fine after that shape disappears.

But, I didn't really get what you mean about the "locked" and "inactive"! If it is not really important then forget about it

forget for now the locked or inactive.
although the extension has strong preventions here and there, nobody can guess what will be in your intro, and where it will be... also what, when, where, how many, etc, OC layers...
and open a layer while the intro is running, may get strange behaviors more like bugs in your page.
try for yourself, while the intro is running, press the tab key until the extension receives the focus and press enter...
again, the extension itself has been carefully planned, but always may be a "but"...
just my cent.

[RZ] wrote: (ps: don't try to make a flash-like site, also flash sites sometimes has individual sections that are loaded on-demand)

Hehe no, am not trying to do that, actually my friend is a senior art director in an international graphic design company and he suggested an intro to explain the logo (once it is published I will post it here).
Personally I don't like flash sites, but those CSS3 animations are suitable (in my opinion) for I want to try to do.
Thanks

[RZ] wrote: and open a layer while the intro is running, may get strange behaviors more like bugs in your page.
try for yourself, while the intro is running, press the tab key until the extension receives the focus and press enter...

Oh ok! you are absolutely right! I didn't take care of this! Thanks a lot for mentioning that
So, the best way now is to use the preloader... I will work on it today
Amazing help man! I really don't know how to thank you

I really don't know how to thank you

you already said it many many times, so you already did it.

Hello [RZ], how are you?

Yesterday I was about to publish my site (constructed on your layer extension), but I bumped into a strange issue!
Here is what happened:
When I started the project, all the base layers and their layers are placed on the same page (index page). You then advised me to take the layers (not the base layers) to different pages and insert a "master-page" object inside each base layer. So I made an exact copy of the project from my desktop to the D: drive, and there, I did what you told me, and it was much easier to edit the content inside the layers.
Now for the new project, I modified some graphical stuff (new logo and some other stuff). I have one of the layers containing a form, I validated each field, and specified the success page in the form properties.
The issue is the form is not submitting the data AND it is not directing to the success page, instead, it is redirecting to the index page again!
I published the old project (which contains everything on the index page) and validated the fields the same way I did for the new project and specified the success page. Now everything works as it should be; the data are submitted and the redirection to the success page occurs correctly.

I really can't seem to spot the issue! I don't really know if the issue occurs due to the new master-pages structure!

Hope you could help me with that.

Thanks a lot

Try using an absolute URL to reach the success page rather than a relative link...e.g http://www.domain.com/success.html

Adendum wrote:Try using an absolute URL to reach the success page rather than a relative link...e.g http://www.domain.com/success.html

Adendum, thanks a lot for the reply

Actually I discovered the problem about an hour ago but I kept on testing stuff before posting here.
The problem was as follows:
Since the master-page that contains the php code, it doesn't inset in in the index page, so all I had to do is to add this code to the start of the index page
Now everything is working like a charm

I will post the link to the website here (since am using [RZ] layer extensions) and I will also post it in the forum page for the sites made with the GREAT WWB

Thank you all for the help and support, I really appreciate it

[RZ],

Here is the link to my site:
http://www.pulsecube.com

Please have a look at it, and tell me what you think

By the way, sometimes, when opening a base layer that contains its layer, the layer is attached to the base layer! This happens randomly in the site, try to open and close some layers and it might happen. If it happens with you, what is the problem?

Thank you

supersonictt wrote:[RZ],Here is the link to my site: http://www.pulsecube.com
Please have a look at it, and tell me what you think

Nice one....impressive, to say the least. Job well done......

But a couple of issues -
1. I can't read any of your headings, damn near invisible!
2. Annoying page shifts due to the vertical scrollbar disappearing then appearing (in Firefox)
3. Permanent horizontal scroll bar in IE unless I go full screen.
4. A couple of images (Smartphones and Webdesign pages) could do with a different colour background - the white is harsh in comparison to your other images.

@supersonictt
i would put the contact form in a inlineframe; this way you can use relative success page instead of an absolute address; moreover, you don't need to publish the whole page in php format.
i tested your site in chrome and i didn't see any issue related to the layers extensions.

@Adendum
Thanks a lot for your feedback, and thank you for spending some time looking into the site.
Well:
1. Concerning the headings, I did it on purpose so no one can read them :p just kidding Well, I tested that on different laptops and desktops and it was readable, mmm, I will try to find a better way other than engraving text, but I really wanted that
2. At what resolution are you previewing the site? I didn't have the time to test it on different resolutions because mine is 1920x1080 which no way for the vertical scrollbar to appear. But of course that's not an excuse. Anyways I guess the only solution for that is to force the vertical scrollbar to stay on by placing a hidden object at more than 1200px height.
3. I am now testing the site using IE9 with 1600x900 but I cannot see any horizontal scrollbar!
4. Do you mean that the white background images do not fit the theme or the other way around? Because I can see that the white ones fit the theme more than the other.
Again, thanks a lot for the great feedback

@[RZ]
As I mentioned in my last post, I solved the issue of the form (honestly I don't know how this simple thing went away from my mind ), but I will try the inlineframe trick
Well, the stuck-layer-to-base issue is not happening now! That's weird hehe
Anyway, maybe that happened because the layers and their base layers do not load fully initially, so if this is the case, am thinking of using the loader extension. What do you think?
Thank you [RZ] for your support, I really appreciate it

Well, concerning the vertical scrollbar, what about setting the overflow-y to scroll?
I tested it and it works (supposedly) without those annoying jumps.
Please if anyone could test that I would really appreciate it.
The index.css (with overflow-y: scroll;) is now published.

Thanks a lot.

maybe that happened because the layers and their base layers do not load fully initially, so if this is the case, am thinking of using the loader extension. What do you think?

i didn't see any issue, so i don't think i can think something about it...
layers are html and are fully loaded as the html loads, and the extension does a strict control about this, i mean the extension doesn't automatically trigger any event until the html/object is loaded, unless you manually add your own code; so i don't think that this is the cause... i would double-check the objects' names/id and your custom code you may added.

[RZ] wrote:

maybe that happened because the layers and their base layers do not load fully initially, so if this is the case, am thinking of using the loader extension. What do you think?

i didn't see any issue, so i don't think i can think something about it...
layers are html and are fully loaded as the html loads, and the extension does a strict control about this, i mean the extension doesn't automatically trigger any event until the html/object is loaded, unless you manually add your own code; so i don't think that this is the cause... i would double-check the objects' names/id and your custom code you may added.

Thanks for the help [RZ]. I guess everything is working well now and I hope this issue doesn't come up again.

Great website. Very well designed. Good to see you using the old BCastr

One thing I noticed, if you close the layer with the contact form, you are left with just the logo. I personally think, it should go to the 1st layer.

I too am a huge fan of RZ's masterpiece

Well done again. Great site. Wish you all the best.

@bendigo
Thanks a lot for the feedback and yes, I like the "old" Bcastr, the good thing about it is that every time you open the first layer (Welcome Layer) it loads the first image. I also removed "<link></link>" from the xml file to prevent the pointer from appearing when the mouse is over the image. I tried hard to find a way when you click on -let's say- "WE BUILD YOUR WEBSITE" it takes you to the "WHAT WE DO - WEBDESIGN", but I failed so that's why I removed the link tags from the xml file.
And about closing any layer and going back to the logo alone, I wanted the dotted square that holds the logo to contain other stuff for the visitor to read, but I couldn't work on it. I might do what you suggested
Thanks again for the kind and motivating words

I am not a huge fan of flash but if I have time
I will fix the XML in the extension to remove the link.

Thanks man don't bother, the extension you made is meant to do this job (link for images), so removing it is easy I think

[RZ}
I found out when this issue is happening.
Try this:
Open the site and hit refresh, then close the tab, open the site again, after the welcome layer opens open contact us and you can see what I was talking about, then open what we do and the same issue happens.
So it if you hit refresh the issue doesn't happen, but re-visiting the site again makes the issue appears.
It happens in Chrome and Firefox, but it never happened in IE9 (weird!).

you have the intro effect, it is based on the old script i gave you in another thread, right?
well, the extension does a strict control about the events triggered at startup.
if i'm not wrong, i suggested you to move your intro to an individual page, and the main content to another page.
when the intro is over, you can redirect to the main page.
your intro is fooling the synchronized startup process of all the layers involved (believe me, it is not so simple as it seems); i'm sorry, but it is a bit difficult to maintain/debug this way.
please divide the intro and the content page, and tell me...
once all is under our control, we can try to experiment adding an intro.

[RZ] wrote:you have the intro effect, it is based on the old script i gave you in another thread, right?
well, the extension does a strict control about the events triggered at startup.
if i'm not wrong, i suggested you to move your intro to an individual page, and the main content to another page.
when the intro is over, you can redirect to the main page.
your intro is fooling the synchronized startup process of all the layers involved (believe me, it is not so simple as it seems); i'm sorry, but it is a bit difficult to maintain/debug this way.
please divide the intro and the content page, and tell me...
once all is under our control, we can try to experiment adding an intro.

Great [RZ], when I go back home I will remove the intro completely and test it, if it works that way then I will find another solution for the intro (I might remove it for good, I see I don't need it at all).
Thanks for the details you gave me, things are clearer now.
Will keep you updated
Thank you

Hello [RZ]
I removed all the events related to the intro, and I set the cube image and the text under to be static. Same problem happens.
I also removed this from the head tag:
<META HTTP-EQUIV="Pragma" CONTENT="no-cache">
<META HTTP-EQUIV="Expires" CONTENT="-1">
but no luck
Well, in the project, the only things that I have (scripts which may do this problem) are:
1. Slideshow as a convayor belt.
2. "No dotted lines after link click" extension by me.prosenjeet.
3. The jguery accordion.
4. The form in the contact us layer.
5. The flash based Bcastr 4.0 Slideshow in the welcome layer.
So, I hope these things can help.

Anyways, did the issue happen with you?

did you see any issue in the online demo?
it is a complex page with deep nested layers and with loop effects... if you can find some issue please let me know.
(btw, i can't guess what happens with your project without seeing what you did)

Well no, no issues at all in your online demo!
Would you like me to send you the project? That is if it is ok with you and you have the TIME to look into it.
Thank you [RZ].

i will try my best, but not right now, i must leave... sorry...

It's ok mate, whenever you can just let me know
Thanks a lot

Well [RZ], in your online demo, am sure that you set the "Group" property in the synchronized layers NOT TO "belongs to all groups".
Well, I set those 3 extensions to "belong to all groups" as I really didn't figure out how to rename the layers and set the group property. This might be the issue in my project.
So, could you please provide an example in WWB on how to setup the groups and name the layers with their base layers?
Thank you again.

*****EDIT*****
Ok, I found out how to specify the group property and name the layers accordingly. I did that to my project and published it with no luck again
I think I will re-build the site again in WWB an name every object properly along with layers and extensions.