We just released a new update (v3.0.4-beta.24)! It is another release of improvements and bug fixes on the road to stability. If you haven’t done so already, please update your app or download the latest version of TastyIgniter to take advantage of everything that’s new. 🎊 What’s New Added support to process refund through the PayRegister API Added support for validating component properties within the admin component editor We have split coupons from the core as an extension 💡 Improvements General UX improvements Location coordinates now gets updated when a location address changes (#516) We now prevent negative pricing on menu items, options and specials (#531) Combined page assets (CSS & JS) now enabled by default when running the backend in production. Deprecated support for plain PHP template files, to be completely removed before v3 Please ensure all child theme template files use the .blade.php file extension That’s it on TastyIgniter v3.0.4-beta.24 highlights. If you’d like to see a full list of improvements and bug fixes included in this release, please see the full release notes . 🛠 Upgrading Always back up your files and database before updating. From the admin dashboard Go to System > Extensions , disable all extensions before upgrading by clicking the square (stop) button on all extensions. Go to System > Updates , click the Ignore button all updates except the TastyIgniter v3.0.4-beta. 24+ update, then click the Update button. Use your newly-upgraded TastyIgniter site! Manually from the command line Follow Step 1 and Step 2 Run the following command at the root of your TastyIgniter installation: composer update php artisan igniter:up php artisan cache:clear if(window.hljsLoader && !document.currentScript.parentNode.hasAttribute('data-s9e-livepreview-onupdate')) { window.hljsLoader.highlightBlocks(document.currentScript.parentNode); } Use your newly-upgraded TastyIgniter site! If you face any issues, please start a new discussion in the Support tag or find us in #support on our Slack . You may find similar issue being discussed but open a new discussion anyway, it helps us get your specific problem solved faster. 😇 Thank You TastyIgniter releases would not be possible without the support of the community, our thanks go out to all of them! Thank you… To everyone who contributed code to this release, to everyone who has helped with testing, to every sponsor, to every Open Collective supporter and Github Sponsor. You guys rock! /Your financial support is a huge source of motivation, it helps provide for stable development hours for TastyIgniter! Help us become a sustainable project by backing us on Open Collective or GitHub !/ Finally, thank /you/ for your continued support, donations, and enthusiasm that keeps us going.

TastyIgniter v3.0.4-beta.24 released

sampoyigi

We just released a new update (v3.0.4-beta.24)! It is another release of improvements and bug fixes on the road to stability.

If you haven’t done so already, please update your app or download the latest version of TastyIgniter to take advantage of everything that’s new.

🎊 What’s New

Added support to process refund through the PayRegister API
Added support for validating component properties within the admin component editor
We have split coupons from the core as an extension

💡 Improvements

General UX improvements
Location coordinates now gets updated when a location address changes (#516)
We now prevent negative pricing on menu items, options and specials (#531)
Combined page assets (CSS & JS) now enabled by default when running the backend in production.
Deprecated support for plain PHP template files, to be completely removed before v3 Please ensure all child theme template files use the .blade.php file extension

That’s it on TastyIgniter v3.0.4-beta.24 highlights. If you’d like to see a full list of improvements and bug fixes included in this release, please see the full release notes .

🛠 Upgrading

Always back up your files and database before updating.

From the admin dashboard

Go to System > Extensions, disable all extensions before upgrading by clicking the square (stop) button on all extensions.
Go to System > Updates, click the Ignore button all updates except the TastyIgniter v3.0.4-beta. 24+ update, then click the Update button.
Use your newly-upgraded TastyIgniter site!

Manually from the command line

Follow Step 1 and Step 2

Run the following command at the root of your TastyIgniter installation:

composer update
php artisan igniter:up
php artisan cache:clear

Use your newly-upgraded TastyIgniter site!

If you face any issues, please start a new discussion in the Support tag or find us in #support on our Slack. You may find similar issue being discussed but open a new discussion anyway, it helps us get your specific problem solved faster.

😇 Thank You

TastyIgniter releases would not be possible without the support of the community, our thanks go out to all of them! Thank you…

To everyone who contributed code to this release, to everyone who has helped with testing, to every sponsor, to every Open Collective supporter and Github Sponsor. You guys rock!

/Your financial support is a huge source of motivation, it helps provide for stable development hours for TastyIgniter! Help us become a sustainable project by backing us on Open Collective or GitHub!/

Finally, thank /you/ for your continued support, donations, and enthusiasm that keeps us going.

uroborus

Hi
i have installed the new version (fresh installation), in the page “reservation” appear: Call to a member function getKey() on null (View: /home2/fordinan/public_html/extensions/igniter/reservation/components/booking/picker_form.blade.php) (View: /home2/fordinan/public_html/extensions/igniter/reservation/components/booking/default.blade.php) (View: /home2/fordinan/public_html/themes/tastyigniter-orange/_pages/reservation/reservation.blade.php)

where is the problem?
Thanks

wakey18

Getting error;
Undefined variable: location (View: /home/******/public_html/themes/phils/_partials/localSearch/default.php) (View: /home/******/public_html/themes/phils/_pages/home.php)

uroborus

sorry i don’t understand…
there is another error when i complete the order

(1/1) Error
Call to a member function each() on null

in Cart.php line 369
at Cart->clearConditions()
in Cart.php line 229
at Cart->destroy(null)
in OrderManager.php line 320
at OrderManager->clearOrder()
in Order.php line 114
at Order->onRun()
in HasComponents.php line 102
at Model->runComponents()
in MainController.php line 308
at MainController->execPageCycle()
in MainController.php line 256
at MainController->runPage(object(Page))
in MainController.php line 192
at MainController->remap('checkout/success/309ccbf9f146f411b92e3f20bb500d1d')
in Controller.php line 85
at Controller->run('checkout/success/309ccbf9f146f411b92e3f20bb500d1d')
in Controller.php line 54
at Controller->callAction('run', array('slug' => 'checkout/success/309ccbf9f146f411b92e3f20bb500d1d'))
in ControllerDispatcher.php line 45
at ControllerDispatcher->dispatch(object(Route), object(Controller), 'run')
in Route.php line 219
at Route->runController()
in Route.php line 176
at Route->run()
in Router.php line 681
at Router->Illuminate\Routing\{closure}(object(Request))
in Pipeline.php line 130
at Pipeline->Illuminate\Pipeline\{closure}(object(Request))
in VerifyCsrfToken.php line 77
at VerifyCsrfToken->handle(object(Request), object(Closure))
in Pipeline.php line 171
at Pipeline->Illuminate\Pipeline\{closure}(object(Request))
in CurrencyMiddleware.php line 33
at CurrencyMiddleware->handle(object(Request), object(Closure))
in Pipeline.php line 171
at Pipeline->Illuminate\Pipeline\{closure}(object(Request))
in CartMiddleware.php line 12
at CartMiddleware->handle(object(Request), object(Closure))
in Pipeline.php line 171
at Pipeline->Illuminate\Pipeline\{closure}(object(Request))
in Localization.php line 40
at Localization->handle(object(Request), object(Closure))
in Pipeline.php line 171
at Pipeline->Illuminate\Pipeline\{closure}(object(Request))
in SubstituteBindings.php line 41
at SubstituteBindings->handle(object(Request), object(Closure))
in Pipeline.php line 171
at Pipeline->Illuminate\Pipeline\{closure}(object(Request))
in ShareErrorsFromSession.php line 49
at ShareErrorsFromSession->handle(object(Request), object(Closure))
in Pipeline.php line 171
at Pipeline->Illuminate\Pipeline\{closure}(object(Request))
in StartSession.php line 56
at StartSession->handle(object(Request), object(Closure))
in Pipeline.php line 171
at Pipeline->Illuminate\Pipeline\{closure}(object(Request))
in AddQueuedCookiesToResponse.php line 37
at AddQueuedCookiesToResponse->handle(object(Request), object(Closure))
in Pipeline.php line 171
at Pipeline->Illuminate\Pipeline\{closure}(object(Request))
in EncryptCookies.php line 67
at EncryptCookies->handle(object(Request), object(Closure))
in Pipeline.php line 171
at Pipeline->Illuminate\Pipeline\{closure}(object(Request))
in Pipeline.php line 105
at Pipeline->then(object(Closure))
in Router.php line 683
at Router->runRouteWithinStack(object(Route), object(Request))
in Router.php line 658
at Router->runRoute(object(Request), object(Route))
in Router.php line 624
at Router->dispatchToRoute(object(Request))
in CoreRouter.php line 20
at CoreRouter->dispatch(object(Request))
in Kernel.php line 170
at Kernel->Illuminate\Foundation\Http\{closure}(object(Request))
in Pipeline.php line 130
at Pipeline->Illuminate\Pipeline\{closure}(object(Request))
in SaveSetting.php line 27
at SaveSetting->handle(object(Request), object(Closure))
in Pipeline.php line 171
at Pipeline->Illuminate\Pipeline\{closure}(object(Request))
in TrustProxies.php line 57
at TrustProxies->handle(object(Request), object(Closure))
in Pipeline.php line 171
at Pipeline->Illuminate\Pipeline\{closure}(object(Request))
in TransformsRequest.php line 21
at TransformsRequest->handle(object(Request), object(Closure))
in Pipeline.php line 171
at Pipeline->Illuminate\Pipeline\{closure}(object(Request))
in ValidatePostSize.php line 27
at ValidatePostSize->handle(object(Request), object(Closure))
in Pipeline.php line 171
at Pipeline->Illuminate\Pipeline\{closure}(object(Request))
in CheckForMaintenanceMode.php line 63
at CheckForMaintenanceMode->handle(object(Request), object(Closure))
in Pipeline.php line 171
at Pipeline->Illuminate\Pipeline\{closure}(object(Request))
in Pipeline.php line 105
at Pipeline->then(object(Closure))
in Kernel.php line 145
at Kernel->sendRequestThroughRouter(object(Request))
in Kernel.php line 110
at Kernel->handle(object(Request))
in index.php line 53

sampoyigi

If you face any issues, please start a new discussion in the Support tag or find us in #support on our Slack.

breaksecurity

Not able to update extension new fresh install

breaksecurity

No error the update process finishes and no updates are applied

tprigas

breaksecurity same here

matando

@sampoyigi With the new release some of the extensions are not being shown as being updated after updating them on the extensions section of the admin panel. Some of the version strings weren’t updated in their respective extension.json files.

I noticed it in the payregister, pages, reservations, user, and FrontEnd extensions but it may be in more.

sampoyigi

matando Erm.. I’ve tried to simplify the process of releasing an extension update to use the latest tag from the extension repo instead of the extension.json version string. The issue is TI core still reading the version tag from the extension.json (should be using the DB version string) after the extension files have been updated. If you look in the extensions DB table you’ll see it has the updated version tag.

I’m working on a new core update to fix the issue.

matando

Ah…… ok. I just happen to do some poking around when I used the update function to update my extensions and noticed they weren’t being updated. The was what I noticed, so I stopped looking further when I saw that. Heh.

sampoyigi

Sorry about the update issues guys! I’ve resolved the version issue with the affected extensions and tagged v3.0.4-beta.24.1

breaksecurity

sampoyigi The problem is still there with socialite extension tasty orange theme maximum orders and mealtimes
I have done even an optimize:clear

breaksecurity

Now it works sampoyigi

breaksecurity

roydeanjr

Yep, updates worked and disappeared as expected.

roydeanjr

Special note for anyone updating to beta.24.2 and Orange Theme 2.7!

If you created and are using a child theme, you MUST open all modified pages, partials and layouts and CHANGE all code in the Markup tab! From something like <?= partial('nav/local_tabs', ['activeTab' => 'menus']); ?> to this @partial('nav/local_tabs', ['activeTab' => 'menus']).

Have fun with this!

wakey18

Fixed that, what could be causing this next error?
Invalid argument supplied for foreach() (View: /home/wankey/public_html/extensions/igniter/frontend/components/slider/default.blade.php) (View: /home/wankey/public_html/themes/phils/_pages/home.php)

breaksecurity

Same error…