A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_files_driver::open($save_path, $name) should either be compatible with SessionHandlerInterface::open(string $path, string $name): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_files_driver.php

Line Number: 132

Backtrace:

File: /home/domains/vol3/447/2714447/user/htdocs/application/controllers/Home.php
Line: 7
Function: __construct

File: /home/domains/vol3/447/2714447/user/htdocs/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_files_driver::close() should either be compatible with SessionHandlerInterface::close(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_files_driver.php

Line Number: 294

Backtrace:

File: /home/domains/vol3/447/2714447/user/htdocs/application/controllers/Home.php
Line: 7
Function: __construct

File: /home/domains/vol3/447/2714447/user/htdocs/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_files_driver::read($session_id) should either be compatible with SessionHandlerInterface::read(string $id): string|false, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_files_driver.php

Line Number: 168

Backtrace:

File: /home/domains/vol3/447/2714447/user/htdocs/application/controllers/Home.php
Line: 7
Function: __construct

File: /home/domains/vol3/447/2714447/user/htdocs/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_files_driver::write($session_id, $session_data) should either be compatible with SessionHandlerInterface::write(string $id, string $data): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_files_driver.php

Line Number: 237

Backtrace:

File: /home/domains/vol3/447/2714447/user/htdocs/application/controllers/Home.php
Line: 7
Function: __construct

File: /home/domains/vol3/447/2714447/user/htdocs/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_files_driver::destroy($session_id) should either be compatible with SessionHandlerInterface::destroy(string $id): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_files_driver.php

Line Number: 317

Backtrace:

File: /home/domains/vol3/447/2714447/user/htdocs/application/controllers/Home.php
Line: 7
Function: __construct

File: /home/domains/vol3/447/2714447/user/htdocs/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_files_driver::gc($maxlifetime) should either be compatible with SessionHandlerInterface::gc(int $max_lifetime): int|false, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_files_driver.php

Line Number: 358

Backtrace:

File: /home/domains/vol3/447/2714447/user/htdocs/application/controllers/Home.php
Line: 7
Function: __construct

File: /home/domains/vol3/447/2714447/user/htdocs/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 282

Backtrace:

File: /home/domains/vol3/447/2714447/user/htdocs/application/controllers/Home.php
Line: 7
Function: __construct

File: /home/domains/vol3/447/2714447/user/htdocs/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: session_set_cookie_params(): Session cookie parameters cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 294

Backtrace:

File: /home/domains/vol3/447/2714447/user/htdocs/application/controllers/Home.php
Line: 7
Function: __construct

File: /home/domains/vol3/447/2714447/user/htdocs/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 304

Backtrace:

File: /home/domains/vol3/447/2714447/user/htdocs/application/controllers/Home.php
Line: 7
Function: __construct

File: /home/domains/vol3/447/2714447/user/htdocs/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 314

Backtrace:

File: /home/domains/vol3/447/2714447/user/htdocs/application/controllers/Home.php
Line: 7
Function: __construct

File: /home/domains/vol3/447/2714447/user/htdocs/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 315

Backtrace:

File: /home/domains/vol3/447/2714447/user/htdocs/application/controllers/Home.php
Line: 7
Function: __construct

File: /home/domains/vol3/447/2714447/user/htdocs/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 316

Backtrace:

File: /home/domains/vol3/447/2714447/user/htdocs/application/controllers/Home.php
Line: 7
Function: __construct

File: /home/domains/vol3/447/2714447/user/htdocs/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 317

Backtrace:

File: /home/domains/vol3/447/2714447/user/htdocs/application/controllers/Home.php
Line: 7
Function: __construct

File: /home/domains/vol3/447/2714447/user/htdocs/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 375

Backtrace:

File: /home/domains/vol3/447/2714447/user/htdocs/application/controllers/Home.php
Line: 7
Function: __construct

File: /home/domains/vol3/447/2714447/user/htdocs/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: session_set_save_handler(): Session save handler cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 110

Backtrace:

File: /home/domains/vol3/447/2714447/user/htdocs/application/controllers/Home.php
Line: 7
Function: __construct

File: /home/domains/vol3/447/2714447/user/htdocs/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: session_start(): Session cannot be started after headers have already been sent

Filename: Session/Session.php

Line Number: 143

Backtrace:

File: /home/domains/vol3/447/2714447/user/htdocs/application/controllers/Home.php
Line: 7
Function: __construct

File: /home/domains/vol3/447/2714447/user/htdocs/index.php
Line: 315
Function: require_once


Deprecated: Optional parameter $status declared before required parameter $type is implicitly treated as a required parameter in /home/domains/vol3/447/2714447/user/htdocs/application/libraries/Tvg_function.php on line 415

Deprecated: Optional parameter $order declared before required parameter $where_conditions is implicitly treated as a required parameter in /home/domains/vol3/447/2714447/user/htdocs/application/core/MY_Model.php on line 147

Deprecated: Optional parameter $order declared before required parameter $where_conditions is implicitly treated as a required parameter in /home/domains/vol3/447/2714447/user/htdocs/application/core/MY_Model.php on line 171

Deprecated: Optional parameter $order declared before required parameter $haystack is implicitly treated as a required parameter in /home/domains/vol3/447/2714447/user/htdocs/application/core/MY_Model.php on line 193

Deprecated: Optional parameter $order declared before required parameter $where_conditions is implicitly treated as a required parameter in /home/domains/vol3/447/2714447/user/htdocs/application/core/MY_Model.php on line 212

Deprecated: Optional parameter $by declared before required parameter $where_conditions is implicitly treated as a required parameter in /home/domains/vol3/447/2714447/user/htdocs/application/core/MY_Model.php on line 212

Deprecated: Optional parameter $select declared before required parameter $where_conditions is implicitly treated as a required parameter in /home/domains/vol3/447/2714447/user/htdocs/application/core/MY_Model.php on line 232

Deprecated: Optional parameter $order declared before required parameter $where_conditions is implicitly treated as a required parameter in /home/domains/vol3/447/2714447/user/htdocs/application/core/MY_Model.php on line 232

Deprecated: Optional parameter $select declared before required parameter $where_conditions is implicitly treated as a required parameter in /home/domains/vol3/447/2714447/user/htdocs/application/core/MY_Model.php on line 260

Deprecated: Optional parameter $order declared before required parameter $where_conditions is implicitly treated as a required parameter in /home/domains/vol3/447/2714447/user/htdocs/application/core/MY_Model.php on line 260

Deprecated: Optional parameter $order declared before required parameter $limit is implicitly treated as a required parameter in /home/domains/vol3/447/2714447/user/htdocs/application/core/MY_Model.php on line 693

Deprecated: Optional parameter $order declared before required parameter $where_conditions is implicitly treated as a required parameter in /home/domains/vol3/447/2714447/user/htdocs/application/core/MY_Model.php on line 871
Blog | Roseline Therapy by Jasmina Connelly
Aug
01
2020

How To Recover After Nose Job

Rhinoplasty, or commonly known as a nose job, is becoming one of the routine surgeries, not only for the nose deviations but also for aesthetic reasons. The procedure itself is quite short, as opposed to the recovery. Swelling is present 3-6 months after the surgery, and it takes a whole year for a nose to heal completely.

 

I followed the rhinoplasty/septoplasty journey of one of my regular clients, where the surgery was more complicated than usual; therefore, recovery was much longer and complicated.

She is only interested in holistic approaches, which is why she became my client in the first place. After reading more on what body went through during and after the surgery, I realised that I might have a way to make the recovery process a lot faster. 

 

I asked her if she would let me try manual, facial lymphatic drainage, followed by wood therapy rollers. She agreed. I was doing lymphatic drainage, in combination with wood therapy, daily. Sometimes I used jade or quartz roller because they were cooler, and the surface was smaller. 

 

The results were so good that we could not believe our eyes. The swelling was going down so quickly, and the treatment itself had such a calming effect on the client, as she used to say, it was like a meditation session.

 

 I believe that each rhinoplasty patients should learn proper techniques to massage their nose beginning three weeks after their nose job. Here's my reasoning to do so:

-The main issue with rhinoplasty is prolonged swelling after the procedure; it can take up to a year to fully heal. Faster the swelling goes away, faster the healing. 

-Swelling that remains in tissue becomes scar tissue.

-Scar tissue can and does blunt and change the nose's surgically created shape from what the Rhinoplasty procedure was able to achieve.

-Removing the swelling, on a daily basis, does decrease the overall amount and time that the swelling is within the nasal.

-Giving patients the ability to massage their noses after rhinoplasty empowers patients to control the asymmetric swelling that occurs after each rhinoplasty and limiting the amount of scar tissue formation. That itself will make the client more confident. Nasal/facial massage, after rhinoplasty, is a no brainer, and I can't imagine why any rhinoplasty surgeon wouldn't spend time explaining to patients how to do it.

 

Since working with that client, I had many other clients who as well showed progress immediately. Some preferred me to do the treatment, and to some, it was more convenient to do the treatment themselves from the comfort of their home.

If you are unsure of the technique yourself, all you need is jade/ quartz /wood facial roller. Because of high interest, we made a short online course on how to do it yourself, in the comfort of your own home, to achieve the best possible result from your rhinoplasty. For more questions, feel free to contact me. 

 

Note: After the first or second lymphatic drainage, all retained liquid in the swollen area, started to move. Lymphatic channels were blocked and could not support such amount of passing lymph fluid. Therefore my client's eye got swollen for two days. We kept going on with the treatment to unblock the lymphatic channels, and enforce the liquid to move. The very next treatment, we noticed tremendous progress, all lymphatic channels started to work efficiently, and every next treatment was a step forward on the healing journey. 

https://roselineacademy.com/wood-therapy-training-uk-maderotherapy-course/

  • nose job, rinosplasty, wood therapy, facial roller, facial massage, facial lymphatic drainage
Share this: