This update gave the following problems:

- error with php5 version, ok I upgraded and worked.
- error when saving an item, error is on "item.php"
- Now you load bootstrap in the templates, this messed with all the code in the site!

Man, I'm really pissed... You install an update and sundelly everything looks different and with a lot of errors! My clients just LOVED that!!

Where do I go to get the old (WORKING FINE) builder? I need this urgent!

Hi @iaron12@gmail.com

Firstly, I'm sorry that you are experiencing these issues but please refrain from using profanities on the forum

Please could you provide the following and I'll report this to admin immediately

1. a complete list of your builder configuration
2. joomla version
3. which environment/platform
4. details of the error you get when saving on item.php
5. details of the errors you receive pertaining to bootstrap

Kind Regards,

Gez

Dear audibleid,

Please, how do I remove all that from listing:

<link rel="stylesheet" href="/v3/administrator/components/com_meusflats/dom/assets/jquery/css/chosen.css" type="text/css" />
<link rel="stylesheet" href="/v3/administrator/components/com_meusflats/dom/assets/bootstrap/css/bootstrap.min.css" type="text/css" />
<link rel="stylesheet" href="/v3/administrator/components/com_meusflats/dom/assets/bootstrap/css/bootstrap-responsive.min.css" type="text/css" />
<link rel="stylesheet" href="/v3/administrator/components/com_meusflats/dom/assets/bootstrap/css/bootstrap-extended.css" type="text/css" />
<link rel="stylesheet" href="/v3/administrator/components/com_meusflats/dom/assets/bootstrap/css/bootstrap-legacy.css" type="text/css" />
<link rel="stylesheet" href="/v3/administrator/components/com_meusflats/dom/assets/bootstrap/css/bootstrap-icons.css" type="text/css" />
<link rel="stylesheet" href="/v3/administrator/components/com_meusflats/css/validationEngine.jquery.css" type="text/css" />
<link rel="stylesheet" href="/v3/components/com_meusflats/css/meusflats.css" type="text/css" />
<link rel="stylesheet" href="/v3/components/com_meusflats/css/toolbar.css" type="text/css" />
<link rel="stylesheet" href="code.jquery.com/ui/1.9.1/themes/base/jquery-ui.css" type="text/css" />
<link rel="stylesheet" href="/v3/media/system/css/calendar-jos.css" type="text/css" title="Verde" media="all" />

You want to remove all of those CSS Stylesheets from the head?

Well, if so, go to your helper.php and comment them out.

Anyway, if you need help with your other issues, please post the details (see my previous message).

Thanks,

Gez

Dear audibleid, thanks for your help

That way I will remove them also from admin. I just want them out in the front-end item/list view.

In that case, I suppose the following will work. Add this to your view:

1. Create an array of the hrefs to remove something like:2. Get the document object3. Remove any occurrences of the $removeCSS while looping through the $doc - for or foreach loop will suffice here. Just check each element of the $doc array passing through the loop using an if(in_array())... If it is in the array, remove it otherwise do nothing.
4. Add push the new $doc back into the document

Very quick post, but this should get you most of the way there...

G

iaron12@gmail.com wrote: You install an update and sundelly everything looks different and with a lot of errors! My clients just LOVED that!!

You dont test before you release to clients?

Cook is somewhat dynamic and yes we can see issues arise that we not there yesterday...
but Cook functionality and support would not have evolved so quickly if we waited for every new function to be fully tested

My Suggestion create a buffer

Step one - Create your working environment
- Project : My Project
- Alias: com_myproject
Download your component install as normal
make the necessary changes as normal
(use the fork directory where possible)

Step two - create your test environment
- save your component under a different name
- change the project title AND alias
- Project: MyTest Project
- Alias: com_mytestproject
- then download it again and install

- I dont make changes to the fork directory in my test component that way i can be assured that it is not one of my overides causing the issue

when you make changes to your cook project and test the changes on your test project

when you are happy
- simply change the project title AND Alias back to com_myproject
- download and install over the top (providing there was no database field changes)

This way you have a copy that you know was working (com_myproject)
Any mysterious issues that were not there yesterday such as one i found tonight (a tool bar was not loading properly) are caught in the com_mytestproject