Dynamic slide show not reading Digital Ocean Spaces URL

What is the correct url format for the image source:

This is the syntax I’ve been using in other places, but the images aren’t coming through.

Thanks

So are there errors in the browser console?

Thanks Teodor…

Seems the slideshow includes are missing on your layout page. Probably you forgot to save it when adding the component on the content page.

The text shows up and slides but the images aren’t.

So are there any other errors in the console?

First answer to your question - Just what you see in those earlier images. Let me know what else you’d like to see.

Second While waiting for your reply I went in and added formatting to the header. Now I get the formatter error. I’ve been fighting this for over a week. The formatter line just disappears from the main layout. Now you’ll an additional 51 errors all related to missing formatter line.

I’ve been edited the main json outside of Wappler to get the formatter line back in there. It works for a while and then disappears again. What is the proper way get this line back in the layout?

You should not edit anything outside of Wappler.
The workflow is really simple.

  1. You work on a content page. You add a component there.
  2. A script line is added in the layout page <head> </head> tags.
  3. You save BOTH content page and layout page.

That’s all.
Problems like these happen when you forget to save the main page and close it later - the script lines added to the main page do not get saved …

Thanks for the process clarification.

  1. What are the proper steps to get this fixed?
  2. Any suggestions on the slideshow errors?

Add the slideshow on the content page again so that it can add its includes on the main layout.

  1. will be fixed then ....

As the slideshow was working - original issue, was why aren’t the images showing - and now the text formatter not working - I chose the path of starting a completely new page.

In the following 2 minutes you will see two more issues: 1) the theme resets itself on the start of a new page, 2) the instead of seeing binding options I see a form offered. For reference, I have deleted and reinstalled Wappler twice last week, did a complete reset of my system before recording this video.

I apologize for so many different issues, but this is what I’ve been working through.

Another bit of information - the AppConnect keeps removing itself & formatter.

When does this happen exactly?

Also … just for test - can you recreate any of the issues if you create a new empty local project and try setting up a main page and a content page out of it?
Something must be really corrupted in this project if such things happen.

I was in the middle of this when you sent your new project request:

I read another post where it was mentioned they saw it happening with every new page. My system was not doing it that frequently until yesterday. Since that post, I cannot start a new page and attempt to a data binding to the new server connect.

Here’s the steps I just did and watched the dmxAppConnect display:

  1. Confirm with the comparison software that dmxappconnect was present.
  2. Open layout file in question - theme in tract.
  3. Add new page - leave it open
  4. Click back to layout file - theme has changed to original style.
  5. Review in layout file in comparison software - no notification of code change
  6. Save new page
  7. Review layout file in comparison software - no notification of code change
  8. Save layout - dmxappconnect line gone.

New project test:

  1. Create new project, new folder
  2. Change a few theme attributes
  3. Add a new page - stable results
  4. Close project
  5. Restart Wappler
  6. Open new page
  7. Add row/column/card
  8. Modify colors
  9. Save - theme remains unchanged.
  10. Create new page - theme remains unchanged.
    Did not create a database connection

Please provide guidance on how to move these pages to a new site or what should I be changing. I’m dead in the water.

@george @Teodor - Help me with the next steps. Thinking I was weeks away from production release to now have to start a new project because I didn’t save the main layout is beyond frustrating.

I don't think that is the issue in your case. If that was the issue, then adding the component again would have inserted the necessary scripts on the main page.
You report some different issues - like appconnect js include being removed on save, theme manager issues etc. it's hard to tell what is wrong with your project as we cannot recreate any of these locally.

I fully understand how hard troubleshooting something like this is remotely. Now add that I’m still working through software, javascript, CSS and accessibility design. I’m willing to upload folder for your analysis. Should I create a bug report for the AppConnect.js disappearance and the theme reset?
What is the best way to deal with the recreating the site? I read somewhere that I should create the page then copy and paste the old page. Suggestions along this line please.

@George @teodor -

  1. What is the best way to deal with the recreating the site? I read somewhere that I should create the page then copy and paste the old page into it.